Triple
T38188630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Ottawa |
E1005389
|
entity |
| Predicate | hasPrimaryHighwayRoute |
P89540
|
FINISHED |
| Object | Highway 401 |
E77970
|
NE 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: Highway 401 | Statement: [Toronto–Ottawa, hasPrimaryHighwayRoute, Highway 401]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryHighwayRoute Context triple: [Toronto–Ottawa, hasPrimaryHighwayRoute, Highway 401]
-
A.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
B.
isPrimaryStateHighway
Indicates that a given road segment is designated as a primary (major) state highway within a state’s road network.
-
C.
isPrimaryNationalHighwayOf
Indicates that a road is the main designated national highway serving a particular country or region.
-
D.
primaryHighwayComponent
chosen
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
E.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
- F. None of above.
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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41852fef9c8190b353b4d36ef3f852 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:29 p.m.