Triple

T6675509
Position Surface form Disambiguated ID Type / Status
Subject Austin FC E151839 entity
Predicate rival P437 FINISHED
Object FC Dallas E10546 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: FC Dallas | Statement: [Austin FC, rival, FC Dallas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FC Dallas
Context triple: [Austin FC, rival, FC Dallas]
  • A. FC Dallas chosen
    FC Dallas is a professional Major League Soccer club based in the Dallas–Fort Worth metroplex.
  • B. San Antonio FC
    San Antonio FC is a professional soccer club based in San Antonio, Texas, that competes in the USL Championship, the second tier of the American soccer league system.
  • C. Houston Dynamo
    Houston Dynamo is a professional soccer club based in Houston, Texas, that competes in Major League Soccer and has won multiple MLS Cup championships.
  • D. El Paso Locomotive FC
    El Paso Locomotive FC is a professional soccer club based in El Paso, Texas, that competes in the USL Championship, the second tier of the American soccer league system.
  • E. Austin FC
    Austin FC is a professional Major League Soccer club based in Austin, Texas, known for its vibrant fan culture and distinctive green-and-black branding.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69c687f830bc81909eb8b04dbb8450b1 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b0f3021481908c2599349eb6ea07 completed March 27, 2026, 4:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c700772aa48190a1356b5a252f6524 completed March 27, 2026, 10:11 p.m.
Created at: March 27, 2026, 2:03 p.m.