Triple
T38435836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 WNBA Finals |
E903938
|
entity |
| Predicate | locationOfDecisiveGame |
P24480
|
FINISHED |
| Object | The Palace of Auburn Hills |
E172015
|
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: The Palace of Auburn Hills | Statement: [2003 WNBA Finals, locationOfDecisiveGame, The Palace of Auburn Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDecisiveGame Context triple: [2003 WNBA Finals, locationOfDecisiveGame, The Palace of Auburn Hills]
-
A.
decisiveGameVenue
chosen
Indicates the location where the final, outcome-determining game of a series or competition is held.
-
B.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
-
C.
victoryLocation
Indicates the place or setting where a victory or triumph occurs.
-
D.
gameOfTheCenturyVenue
Indicates the venue where the event known as the "Game of the Century" took place.
-
E.
decisiveGameRoadTeam
Indicates that the game was a decisive or series-clinching matchup in which the team playing on the road participated as the road team.
- F. None of above.
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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c296ca2081908d0b867e8a5c70ca |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.