Triple
T4740525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartford Crossing |
E105227
|
entity |
| Predicate | directionOfBridgeTraffic |
P3915
|
FINISHED |
| Object | northbound |
—
|
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: northbound | Statement: [Dartford Crossing, directionOfBridgeTraffic, northbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfBridgeTraffic Context triple: [Dartford Crossing, directionOfBridgeTraffic, northbound]
-
A.
crossingDirection
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
trafficDirection
chosen
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
tollBridge
Indicates that passage across a bridge requires payment of a toll or fee.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.