Triple
T3969679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1956 Winter Olympics |
E92297
|
entity |
| Predicate | usedOlympicFlame |
P15166
|
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: [1956 Winter Olympics, usedOlympicFlame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOlympicFlame Context triple: [1956 Winter Olympics, usedOlympicFlame, true]
-
A.
olympicCauldronLighter
Indicates the person or entity that performs the ceremonial act of lighting the Olympic cauldron at the start of the Olympic Games.
-
B.
olympicFlameFirstLitInLondon
Indicates that the Olympic flame was first lit in the city of London.
-
C.
hasOlympicTorchRelay
chosen
Indicates that an Olympic Torch Relay event is held in association with a particular place, event, or edition of the Olympic Games.
-
D.
lightingOfEternalFlameInitiatedBy
Indicates that the action of lighting an eternal flame is initiated or carried out by a specified agent or entity.
-
E.
hasOlympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Olympic Games or Olympic movement.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.