Triple
T749789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin |
E15420
|
entity |
| Predicate | sportsTeam |
P330
|
FINISHED |
| Object | Austin FC |
E151839
|
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: Austin FC | Statement: [Austin, sportsTeam, Austin FC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Austin FC Context triple: [Austin, sportsTeam, Austin FC]
-
A.
Austin FC
chosen
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.
-
B.
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.
-
C.
FC Dallas
FC Dallas is a professional Major League Soccer club based in the Dallas–Fort Worth metroplex.
-
D.
St. Louis City SC
St. Louis City SC is a professional soccer club competing in Major League Soccer and representing the city of St. Louis.
-
E.
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.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6304e0c8190827fb57c5cac2da9 |
completed | March 1, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acc5f8bc2081908f7d2435ce43fdc4 |
completed | March 8, 2026, 12:42 a.m. |
Created at: March 1, 2026, 7:37 p.m.