Text REtrieval Conference (TREC)
|
Organization Name: IBM T.J. Watson Research Center | Run ID: ibmg97b |
Section 1.0 System Summary and Timing |
---|
Section 1.1 System Information |
Hardware Model Used for TREC Experiment:IBM RS/6000 42T System Use:SHARED Total Amount of Hard Disk Storage:15 Gb Total Amount of RAM:128 MB Clock Rate of CPU:120 MHz |
Section 1.2 System Comparisons |
Amount of developmental "Software Engineering":ALL List of features that are not present in the system, but would have been beneficial to have:Ability to execute Boolean queries; Ability to handle phrases; Ability to handle fields within the document. List of features that are present in the system, and impacted its performance, but are not detailed within this form:The system performs morphological expansion at run time instead of stemming at indexing time. |
Section 2.0 Construction of Indices, Knowledge Bases, and Other Data Structures |
---|
Length of the stopword list:251 words Type of Stemming:NONE Controlled Vocabulary:NO Term weighting:NO
Phrase discovery:NO
Type of Spelling Correction:NONE Manually-Indexed Terms:NO Proper Noun Identification:NO Syntactic Parsing:NO Tokenizer:YES Word Sense Disambiguation:NO Other technique:NO Additional comments: |
Section 3.0 Statistics on Data Structures Built from TREC Text |
---|
Section 3.1 First Data Structure |
Structure Type:INVERTED INDEX Type of other data structure used: Brief description of method using other data structure: Total storage used:1.17 Gb Total computer time to build:3.03 hours Automatic process:YES Manual hours required:hours Type of manual labor:NONE Term positions used:YES Only single terms used:YES Concepts (vs. single terms) represented:NO
Type of representation: Auxilary files used:NO
Additional comments: |
Section 3.2 Second Data Structure |
Structure Type: Type of other data structure used: Brief description of method using other data structure: Total storage used:Gb Total computer time to build:hours Automatic process: Manual hours required:hours Type of manual labor:NONE Term positions used: Only single terms used: Concepts (vs. single terms) represented:
Type of representation: Auxilary files used:
Additional comments: |
Section 3.3 Third Data Structure |
Structure Type: Type of other data structure used: Brief description of method using other data structure: Total storage used:Gb Total computer time to build:hours Automatic process: Manual hours required:hours Type of manual labor:NONE Term positions used: Only single terms used: Concepts (vs. single terms) represented:
Type of representation: Auxilary files used:
Additional comments: |
Section 4.0 Data Built from Sources Other than the Input Text |
---|
File type:NONE Domain type:DOMAIN INDEPENDENT Total Storage:Gb Number of Concepts Represented:concepts Type of representation:NONE Automatic or Manual:
Type of Manual Labor used:NONE Additional comments: |
File is:NONE Total Storage:Gb Number of Concepts Represented:concepts Type of representation:NONE Additional comments: |
Section 5.0 Computer Searching |
---|
Average computer time to search (per query): 14.2 CPU seconds |
Times broken down by component(s): |
Section 5.1 Searching Methods |
Vector space model:NO Probabilistic model:YES Cluster searching:NO N-gram matching:NO Boolean matching:NO Fuzzy logic:NO Free text scanning:NO Neural networks:NO Conceptual graphic matching:NO Other:NO Additional comments: |
Section 5.2 Factors in Ranking |
Term frequency:YES Inverse document frequency:NO Other term weights:NO Semantic closeness:NO Position in document:NO Syntactic clues:NO Proximity of terms:YES Information theoretic weights:NO Document length:YES Percentage of query terms which match:NO N-gram frequency:NO Word specificity:NO Word sense frequency:NO Cluster distance:NO Other:NO Additional comments:The system incorporates scores for Lexical Affinities into the document rank. Lexical Affinities are pairs of words that occur within a distance of 5 words from each other within the same sentence. |
Section 6.0 Query Construction |
---|
Section 6.1 Automatically Built Queries for Ad-hoc Tasks |
Topic fields used: TITLE DESCRIPTION Average computer time to build query 0.023 CPU seconds Term weighting (weights based on terms in topics): NO Phrase extraction from topics: NO Syntactic parsing of topics: NO Word sense disambiguation: NO Proper noun identification algorithm: NO Tokenizer: YES Expansion of queries using previously constructed data structures: NO Automatic addition of: NONE |
Section 6.2 Manually Constructed Queries for Ad-hoc Tasks |
Topic fields used: Average time to build query? minutes Type of query builder: Tool used to build query: Method used in intial query construction? Total CPU time for all iterations: seconds Clock time from initial construction of query to completion of final query: minutes Average number of iterations: Average number of documents examined per iteration: Minimum number of iterations: Maximum number of iterations: The end of an iteration is determined by: Automatic term reweighting from relevant documents: Automatic query expansion from relevant documents: Other automatic methods: Manual methods used: |
Disclaimer: Contents of this online document are not necessarily the official views of, nor endorsed by the U.S. Government, the Department of Commerce, or NIST. |