Triple
T36676290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 NHL All-Star Game |
E905548
|
entity |
| Predicate | skillsCompetitionVenue |
P21366
|
FINISHED |
| Object | Amalie Arena |
—
|
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: Amalie Arena | Statement: [2018 NHL All-Star Game, skillsCompetitionVenue, Amalie Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillsCompetitionVenue Context triple: [2018 NHL All-Star Game, skillsCompetitionVenue, Amalie Arena]
-
A.
skillsCompetitionEvent
Indicates that a competitive event is held to assess and compare participants’ skills or abilities.
-
B.
locationOfCompetition
chosen
Indicates the place or venue where a competition or contest takes or took place.
-
C.
indoorCompetition
Indicates that a competitive event or contest takes place indoors rather than outdoors.
-
D.
competitionHeld
Indicates that a competitive event takes place or is organized at a particular time and/or location.
-
E.
competitionPlacement
Indicates the relative rank or position an entity achieved in a competition or contest.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7a311588190928d93aa1eab4d7e |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.