Triple
T31494677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Hope |
E803502
|
entity |
| Predicate | highwayJunctionOf |
P41155
|
FINISHED |
| Object | Trans-Canada Highway |
—
|
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: Trans-Canada Highway | Statement: [District of Hope, highwayJunctionOf, Trans-Canada Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highwayJunctionOf Context triple: [District of Hope, highwayJunctionOf, Trans-Canada Highway]
-
A.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
B.
expresswayInterchange
Indicates a road connection where an expressway intersects with another road or expressway, allowing vehicles to transfer between them.
-
C.
roadJunctionRelation
chosen
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
D.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e8f46c819085d3019e45989d9c |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:40 p.m.