Triple
T9258279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Placid Olympic Museum |
E222500
|
entity |
| Predicate | highlightsEvent |
P6628
|
FINISHED |
| Object | 1980 "Miracle on Ice" ice hockey game |
—
|
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: 1980 "Miracle on Ice" ice hockey game | Statement: [Lake Placid Olympic Museum, highlightsEvent, 1980 "Miracle on Ice" ice hockey game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsEvent Context triple: [Lake Placid Olympic Museum, highlightsEvent, 1980 "Miracle on Ice" ice hockey game]
-
A.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
eventFocus
Indicates that a particular event is the primary subject of attention, analysis, or relevance within a given context or dataset.
-
C.
featuresEvent
chosen
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
D.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b660448190b6bc04beff0f5512 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.