Triple
T34932981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 Stanley Cup playoffs |
E1007491
|
entity |
| Predicate | finalGame4Venue |
P115926
|
FINISHED |
| Object | Chicago Stadium |
—
|
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: Chicago Stadium | Statement: [1992 Stanley Cup playoffs, finalGame4Venue, Chicago Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGame4Venue Context triple: [1992 Stanley Cup playoffs, finalGame4Venue, Chicago Stadium]
-
A.
fourthRoundVenue
Indicates the location or venue where the fourth round of an event, competition, or series takes place.
-
B.
fourthBoutVenue
Indicates the venue or location where the fourth bout or match in a sequence takes place.
-
C.
finalSeasonAtVenue
Indicates that a particular season is the last one in which an entity (such as a team or event) takes place at a given venue.
-
D.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
E.
venueOfFinalMatch
chosen
Indicates the location where the final match of a competition or tournament is held.
- F. None of above.
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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4 p.m.