Triple
T4112173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XXIV Olympic Winter Games |
E90200
|
entity |
| Predicate | officialTorch |
P12886
|
FINISHED |
| Object | Flying |
—
|
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: Flying | Statement: [XXIV Olympic Winter Games, officialTorch, Flying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialTorch Context triple: [XXIV Olympic Winter Games, officialTorch, Flying]
-
A.
roleInOperationTorch
Indicates that an entity participated in or held a specific role in Operation Torch, the Allied invasion of North Africa during World War II.
-
B.
hasTorchRelay
chosen
Indicates that an event or entity includes or is associated with a torch relay as part of its activities or proceedings.
-
C.
officialScriptOf
Indicates that one writing system is formally designated as the standard or legally recognized script used for a particular language, region, or entity.
-
D.
olympicCauldronLighter
Indicates the person or entity that performs the ceremonial act of lighting the Olympic cauldron at the start of the Olympic Games.
-
E.
officialRepositoryFor
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.