Triple
T38188632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Ottawa |
E1005389
|
entity |
| Predicate | hasAlternativeHighwayRoute |
P19868
|
FINISHED |
| Object | Highway 7 |
—
|
NE NERFINISHED |
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: Highway 7 | Statement: [Toronto–Ottawa, hasAlternativeHighwayRoute, Highway 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeHighwayRoute Context triple: [Toronto–Ottawa, hasAlternativeHighwayRoute, Highway 7]
-
A.
alternativeRoute
chosen
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
B.
trailAlternativeName
Indicates that an entity (such as a trail) is known by an alternative or secondary name.
-
C.
hasAlternateTake
Indicates that one entity is an alternative version or different take of another, typically representing a variant recording, shot, or rendition of the same underlying content.
-
D.
hasExpresswaySection
Indicates that an entity includes, contains, or is associated with a specific section or segment of an expressway.
-
E.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:29 p.m.