Triple
T33489907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 MLS Supporters' Shield |
E857709
|
entity |
| Predicate | winnerCurrentName |
P185245
|
FINISHED |
| Object | Sporting Kansas City |
—
|
NE NERFINISHED |
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: Sporting Kansas City | Statement: [2000 MLS Supporters' Shield, winnerCurrentName, Sporting Kansas City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerCurrentName Context triple: [2000 MLS Supporters' Shield, winnerCurrentName, Sporting Kansas City]
-
A.
winnerFullName
Indicates the full personal name of the entity that is the winner in a given event or competition.
-
B.
winnerBirthName
Indicates the full birth name of the entity that is identified as the winner in a given context.
-
C.
winnerNickname
Indicates the nickname used to refer to the entity that has won a particular contest, event, or competition.
-
D.
lastWinner
Indicates that one entity is the most recent winner in a sequence of competitions, contests, or events involving the other entity.
-
E.
winnerCharacter
Indicates that one entity is the character who wins or is victorious in a given event, contest, or situation involving another entity.
- F. None of above. chosen
Provenance (4 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 1, 2026, 1:38 a.m.