Triple
T9866820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Mann Bridge |
E239853
|
entity |
| Predicate | directionalLanes |
P83805
|
FINISHED |
| Object | 5 lanes each direction |
—
|
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: 5 lanes each direction | Statement: [Port Mann Bridge, directionalLanes, 5 lanes each direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionalLanes Context triple: [Port Mann Bridge, directionalLanes, 5 lanes each direction]
-
A.
laneCount
Indicates the number of parallel lanes associated with a given road or roadway segment.
-
B.
laneStructure
chosen
Indicates the structural organization and configuration of lanes within a roadway or traffic facility.
-
C.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
-
D.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
E.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d209ac8190b9bc9ff017a132da |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.