Triple
T37133997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia Highway 8 |
E919604
|
entity |
| Predicate | connectsToHighwayAtMerritt |
P12245
|
FINISHED |
| Object | British Columbia Highway 5 |
—
|
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: British Columbia Highway 5 | Statement: [British Columbia Highway 8, connectsToHighwayAtMerritt, British Columbia Highway 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToHighwayAtMerritt Context triple: [British Columbia Highway 8, connectsToHighwayAtMerritt, British Columbia Highway 5]
-
A.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
B.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
C.
atJunctionOf
Indicates that something is located at or directly connected to the point where two or more paths, roads, or lines meet.
-
D.
isThoroughfareFor
Indicates that something serves as a route or passageway used for travel or transportation between places.
-
E.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:15 p.m.