Triple
T87764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourne Bridge |
E1763
|
entity |
| Predicate | hasTrafficDirection |
P4069
|
FINISHED |
| Object | bidirectional |
—
|
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: bidirectional | Statement: [Bourne Bridge, hasTrafficDirection, bidirectional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrafficDirection Context triple: [Bourne Bridge, hasTrafficDirection, bidirectional]
-
A.
hasLanes
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
B.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
-
C.
drivingSide
Indicates which side of the road (left or right) vehicles are required to drive on in a given jurisdiction.
-
D.
originalTrafficType
Indicates the initial category or source classification of traffic before any changes, redirects, or reattributions occur.
-
E.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
- F. None of above. chosen
Provenance (4 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2503d304c8190a0034ffa4a38a501 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb6da2c8190a33d144d219f7abe |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2503c12808190a3cbb7b171f466f0 |
completed | Feb. 28, 2026, 2:17 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.