Triple
T19136180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic torch relay |
E468440
|
entity |
| Predicate | torchIsLitBy |
P12120
|
FINISHED |
| Object | sun’s rays in Olympia |
—
|
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: sun’s rays in Olympia | Statement: [Olympic torch relay, torchIsLitBy, sun’s rays in Olympia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchIsLitBy Context triple: [Olympic torch relay, torchIsLitBy, sun’s rays in Olympia]
-
A.
hasTorch
Indicates that one entity possesses or is currently holding a torch in relation to another context or entity.
-
B.
torchLighter
chosen
Indicates that one entity lights, ignites, or operates a torch for another entity or in relation to another entity.
-
C.
hasTorchRelay
Indicates that an event or entity includes or is associated with a torch relay as part of its activities or proceedings.
-
D.
torchLighterOccupation
Indicates that one entity’s occupation or job role is that of a torch lighter in relation to the other entity.
-
E.
hasLanternLightSource
Indicates that an entity uses a lantern as its source of light.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ed0704819098be992297320cc9 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.