Triple
T36727070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 NHL All-Star Game |
E907222
|
entity |
| Predicate | hostSelectionAnnouncementYear |
P13803
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [2019 NHL All-Star Game, hostSelectionAnnouncementYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSelectionAnnouncementYear Context triple: [2019 NHL All-Star Game, hostSelectionAnnouncementYear, 2017]
-
A.
selectionYear
Indicates the year in which an entity was chosen or selected for a particular role, status, or inclusion.
-
B.
hostCitySelectionYear
chosen
Indicates the year in which a city was selected or designated to serve as the host for a particular event or activity.
-
C.
hostedEventYear
Indicates the specific year in which an entity hosted a particular event.
-
D.
policyAnnouncementYear
Indicates the year in which a specific policy was formally announced.
-
E.
expansionAnnouncementYear
Indicates the year in which an expansion (such as a project, product, or service extension) was officially announced.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:12 p.m.