Triple
T19136181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic torch relay |
E468440
|
entity |
| Predicate | torchLightingMethod |
P82026
|
FINISHED |
| Object | parabolic mirror |
—
|
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: parabolic mirror | Statement: [Olympic torch relay, torchLightingMethod, parabolic mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchLightingMethod Context triple: [Olympic torch relay, torchLightingMethod, parabolic mirror]
-
A.
torchLightingLocation
Indicates the location where a torch is or should be lit in relation to another entity or environment.
-
B.
torchLighter
Indicates that one entity lights, ignites, or operates a torch for another entity or in relation to another entity.
-
C.
lightGenerationMethod
chosen
Indicates the method or process by which light is produced or generated.
-
D.
torchLighterOccupation
Indicates that one entity’s occupation or job role is that of a torch lighter in relation to the other entity.
-
E.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
- 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.