Triple
T26133996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Asian Games |
E659323
|
entity |
| Predicate | torchRelaySymbol |
P29545
|
FINISHED |
| Object | eternal flame from Mrapen |
—
|
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: eternal flame from Mrapen | Statement: [2018 Asian Games, torchRelaySymbol, eternal flame from Mrapen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchRelaySymbol Context triple: [2018 Asian Games, torchRelaySymbol, eternal flame from Mrapen]
-
A.
torchRelay
Indicates a sequential passing of a ceremonial torch from one participant or location to another as part of a relay event.
-
B.
torchRelayFinalePerformer
Indicates that an entity performs the final segment or ceremonial act in a torch relay event.
-
C.
torchRelayNotableFeature
chosen
Indicates a notable characteristic, highlight, or distinctive aspect associated with a torch relay event or segment.
-
D.
torchRelayRegion
Indicates that an Olympic torch relay segment takes place within or is associated with a specific geographic region.
-
E.
torchType
Indicates the specific kind or category of torch associated with an 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b96085c81908a43574f4e07e70d |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:16 p.m.