Triple
T11304208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia Highway 12 |
E267672
|
entity |
| Predicate | roadDirectionGeneral |
P44884
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [British Columbia Highway 12, roadDirectionGeneral, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDirectionGeneral Context triple: [British Columbia Highway 12, roadDirectionGeneral, north–south]
-
A.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
B.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
C.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
hasStreetDirection
chosen
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a5c3788190ba54eda514b97903 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.