System Summary and Timing Organization Name: IRIT TOULOUSE List of Run ID's: mercure-r1, mercure-r2, mercure-a1, mercure-a2 Construction of Indices, Knowledge Bases, and other Data Structures Methods Used to build Data Structures - Length (in words) of the stopword list: 572 - Controlled Vocabulary?: NO - Stemming Algorithm: Porter - Morphological Analysis: NO - Term Weighting: YES - Phrase Discovery?: NO - Syntactic Parsing?: NO - Word Sense Disambiguation?: NO - Heuristic Associations (including short definition)?: NO - Spelling Checking (with manual correction)?: NO - Spelling Correction?: NO - Proper Noun Identification Algorithm?: NO - Tokenizer?: - Patterns which are tokenized: NO - Manually-Indexed Terms?: NO - Other Techniques for building Data Structures: None Statistics on Data Structures built from TREC Text - Inverted index - Run ID: mercure-r1, mercure-r2 - Total Storage (in MB): 250 - Total Computer Time to Build (in hours): ~12 - Automatic Process? (If not, number of manual hours): YES - Use of Term Positions?: NO - Only Single Terms Used?: YES - Inverted index - Run ID: mercure-a1, mercure-a2 - Total Storage (in MB): 330 - Total Computer Time to Build (in hours): ~17 - Automatic Process? (If not, number of manual hours): YES - Use of Term Positions?: NO - Only Single Terms Used?: YES - Clusters - N-grams, Suffix arrays, Signature Files - Knowledge Bases - Use of Manual Labor - Special Routing Structures - Other Data Structures built from TREC text Query construction Automatically Built Queries (Ad-Hoc) - Topic Fields Used: mercure-a2 (description), mercure-a1 (ALL) - Average Computer Time to Build Query (in cpu seconds): ~ 1 second/query - Method used in Query Construction - Term Weighting (weights based on terms in topics)?: YES - Phrase Extraction from Topics?: NO - Syntactic Parsing of Topics?: NO - Word Sense Disambiguation?: NO - Proper Noun Identification Algorithm?: NO - Tokenizer?: - Patterns which are Tokenized: NO - Heuristic Associations to Add Terms?: not used - Expansion of Queries using Previously-Constructed Data Structure?: - Automatic Addition of Boolean Connectors or Proximity Operators?: NO Automatically Built Queries (Routing) - Topic Fields Used: ALL - Average Computer Time to Build Query (in cpu seconds): ~ 1 seconde/query - Method used in Query Construction - Terms Selected From - Topics: YES - All Training Documents: YES - Only Documents with Relevance Judgments: YES - Term Weighting with Weights Based on terms in - Topics: YES - All Training Documents: YES - Documents with Relevance Judgments: YES - Phrase Extraction from - Syntactic Parsing - Word Sense Disambiguation using - Proper Noun Identification Algorithm from - Tokenizer - Heuristic Associations to Add Terms from - Expansion of Queries using Previously-Constructed Data Structure: - Automatic Addition of Boolean connectors or Proximity Operators using information from Searching Search Times - Run ID: mercure-r1, mercure-r2, mercure-a1, mercure-a2 - Computer Time to Search (Average per Query, in CPU seconds): ~2-5second/query Machine Searching Methods - Neural Networks?: YES Factors in Ranking - Term Frequency?: YES - Inverse Document Frequency?: YES - Document Length?: YES - Other: neural activation Machine Information - Machine Type for TREC Experiment: Sun (Ultra) - Amount of Hard Disk Storage (in MB): 5GB - Amount of RAM (in MB): 64 - Clock Rate of CPU (in MHz): 128