Triple
T30956723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio 2016 Olympic Torch Relay |
E788694
|
entity |
| Predicate | torchLightingLocationBeforeRelay |
P29638
|
FINISHED |
| Object | Olympia, Greece |
—
|
NE NERFINISHED |
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: Olympia, Greece | Statement: [Rio 2016 Olympic Torch Relay, torchLightingLocationBeforeRelay, Olympia, Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchLightingLocationBeforeRelay Context triple: [Rio 2016 Olympic Torch Relay, torchLightingLocationBeforeRelay, Olympia, Greece]
-
A.
torchLightingLocation
chosen
Indicates the location where a torch is or should be lit in relation to another entity or environment.
-
B.
lightOrganLocation
Indicates the anatomical location or placement of a light-producing organ within or on an organism.
-
C.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
-
D.
lightingTime
Indicates the time at which a lighting event or illumination occurs or is scheduled.
-
E.
torchLighterOccupation
Indicates that one entity’s occupation or job role is that of a torch lighter in relation to the other 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:54 p.m.