Triple
T1738198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 NHL All-Star Game |
E37967
|
entity |
| Predicate | skillsCompetitionHeld |
P10409
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [1996 NHL All-Star Game, skillsCompetitionHeld, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillsCompetitionHeld Context triple: [1996 NHL All-Star Game, skillsCompetitionHeld, true]
-
A.
skillsCompetitionEvent
chosen
Indicates that a competitive event is held to assess and compare participants’ skills or abilities.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
E.
organizedCompetitionIn
Indicates that an entity arranged, managed, or hosted a competition that took place in a specified location.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.