Triple
T28343542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Road 50 |
E717883
|
entity |
| Predicate | hasHighwayClassification |
P165312
|
FINISHED |
| Object | regional road in Ontario |
—
|
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: regional road in Ontario | Statement: [Regional Road 50, hasHighwayClassification, regional road in Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighwayClassification Context triple: [Regional Road 50, hasHighwayClassification, regional road in Ontario]
-
A.
hasRoadClass
chosen
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
-
B.
isCarriagewayOf
Indicates that a given road segment functions as a carriageway that forms part of, or belongs to, a larger road or route.
-
C.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
D.
isPartOfHighwaySystem
Indicates that something belongs to, or is included within, a designated highway system.
-
E.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 28, 2026, 12:41 a.m.