Triple
T2079157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Summer Olympics |
E45198
|
entity |
| Predicate | torchRelayDistance |
P27195
|
FINISHED |
| Object | 27000 kilometres |
—
|
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: 27000 kilometres | Statement: [2000 Summer Olympics, torchRelayDistance, 27000 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchRelayDistance Context triple: [2000 Summer Olympics, torchRelayDistance, 27000 kilometres]
-
A.
torchRelay
Indicates a sequential passing of a ceremonial torch from one participant or location to another as part of a relay event.
-
B.
torchRelayEndDate
Indicates the date on which a torch relay event or sequence officially concludes.
-
C.
distanceMetric
chosen
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
D.
torchRelayNotableFeature
Indicates a notable characteristic, highlight, or distinctive aspect associated with a torch relay event or segment.
-
E.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba3307308190ab329fe3192b2e0f |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.