Triple
T10998534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chattanooga FC |
E259945
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object |
Nashville FC
Nashville FC is a Tennessee-based soccer club known for its regional rivalry with Chattanooga FC and its role in the growing American lower-division and professional soccer landscape.
|
E898852
|
NE FINISHED |
How this triple was built (4 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: Nashville FC | Statement: [Chattanooga FC, hasRival, Nashville FC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nashville FC Context triple: [Chattanooga FC, hasRival, Nashville FC]
-
A.
Nashville SC
Nashville SC is a professional soccer club based in Nashville, Tennessee, that competes in Major League Soccer.
-
B.
Memphis 901 FC
Memphis 901 FC is a professional soccer club based in Memphis, Tennessee, competing in the USL Championship.
-
C.
North Carolina FC
North Carolina FC is a professional soccer club based in the Raleigh–Durham area that competes in the USL Championship.
-
D.
Charlotte FC
Charlotte FC is a professional soccer club based in Charlotte, North Carolina, competing in Major League Soccer.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Nashville FC Triple: [Chattanooga FC, hasRival, Nashville FC]
Generated description
Nashville FC is a Tennessee-based soccer club known for its regional rivalry with Chattanooga FC and its role in the growing American lower-division and professional soccer landscape.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Nashville FC Target entity description: Nashville FC is a Tennessee-based soccer club known for its regional rivalry with Chattanooga FC and its role in the growing American lower-division and professional soccer landscape.
-
A.
Nashville SC
Nashville SC is a professional soccer club based in Nashville, Tennessee, that competes in Major League Soccer.
-
B.
Memphis 901 FC
Memphis 901 FC is a professional soccer club based in Memphis, Tennessee, competing in the USL Championship.
-
C.
North Carolina FC
North Carolina FC is a professional soccer club based in the Raleigh–Durham area that competes in the USL Championship.
-
D.
Charlotte FC
Charlotte FC is a professional soccer club based in Charlotte, North Carolina, competing in Major League Soccer.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d3b08c81909376cd73c42fcefe |
completed | April 9, 2026, 12:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e34530ada081909dc58ff0261e93e7 |
completed | April 18, 2026, 8:47 a.m. |
| NEDg | Description generation | batch_69e35570b0bc8190a939b0c8e3ce8105 |
completed | April 18, 2026, 9:57 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69e359508a388190a16d48a17015e13e |
completed | April 18, 2026, 10:13 a.m. |
Created at: April 8, 2026, 9:24 p.m.