Triple
T6794280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giancarlo Peris |
E156012
|
entity |
| Predicate | torchRelaySegment |
P29545
|
FINISHED |
| Object | final segment in the Olympic Stadium, Rome |
—
|
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: final segment in the Olympic Stadium, Rome | Statement: [Giancarlo Peris, torchRelaySegment, final segment in the Olympic Stadium, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchRelaySegment Context triple: [Giancarlo Peris, torchRelaySegment, final segment in the Olympic Stadium, Rome]
-
A.
torchRelay
Indicates a sequential passing of a ceremonial torch from one participant or location to another as part of a relay event.
-
B.
torchRelayNotableFeature
chosen
Indicates a notable characteristic, highlight, or distinctive aspect associated with a torch relay event or segment.
-
C.
torchRelayEndDate
Indicates the date on which a torch relay event or sequence officially concludes.
-
D.
torchRelayHostCity
Indicates that a city serves as a host location for a segment or stage of the Olympic torch relay.
-
E.
torchLighter
Indicates that one entity lights, ignites, or operates a torch for another entity or in relation to 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c59648819081736d27d52d957f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.