Triple
T2349764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indy Eleven |
E47418
|
entity |
| Predicate | hasRivalry |
P748
|
FINISHED |
| Object | Louisville City FC |
E136964
|
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: Louisville City FC | Statement: [Indy Eleven, hasRivalry, Louisville City FC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Louisville City FC Context triple: [Indy Eleven, hasRivalry, Louisville City FC]
-
A.
Louisville City FC
chosen
Louisville City FC is a professional soccer club based in Louisville, Kentucky, that competes in the USL Championship, the second tier of the American soccer pyramid.
-
B.
Racing Louisville FC
Racing Louisville FC is a professional women's soccer club based in Louisville, Kentucky, that competes in the National Women's Soccer League.
-
C.
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.
-
D.
Indy Eleven
Indy Eleven is a professional American soccer club that competes in the USL Championship and is based in Indianapolis, Indiana.
-
E.
Valour FC
Valour FC is a professional soccer club based in Winnipeg, Manitoba, that competes in the Canadian Premier League.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc6cfffc88190b49433f52581420e |
completed | March 7, 2026, 6:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae962cb7988190bb2bb23191acf6ae |
completed | March 9, 2026, 9:43 a.m. |
Created at: March 4, 2026, 7:54 p.m.