Triple
T19136174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic torch relay |
E468440
|
entity |
| Predicate | routeVariesBy |
P134570
|
FINISHED |
| Object | host city |
—
|
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: host city | Statement: [Olympic torch relay, routeVariesBy, host city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeVariesBy Context triple: [Olympic torch relay, routeVariesBy, host city]
-
A.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
routeAffected
Indicates that a transportation route is impacted or disrupted in some way, such as by delays, closures, or changes in service.
-
D.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
E.
routeMayInclude
Indicates that a given route can optionally pass through, contain, or involve a specified segment, location, or element as part of its path.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.