Triple
T3631660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junction 1 of M60 motorway |
E76968
|
entity |
| Predicate | carriagewayDirection |
P3915
|
FINISHED |
| Object | clockwise |
—
|
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: clockwise | Statement: [Junction 1 of M60 motorway, carriagewayDirection, clockwise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriagewayDirection Context triple: [Junction 1 of M60 motorway, carriagewayDirection, clockwise]
-
A.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
-
B.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
C.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
trafficDirection
chosen
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30251d881908284edeb7fe69ad8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.