Triple
T24947722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straiton |
E624236
|
entity |
| Predicate | nearMotorwayRingRoad |
P49834
|
FINISHED |
| Object | Edinburgh City Bypass (A720) |
—
|
NE NERFINISHED |
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: Edinburgh City Bypass (A720) | Statement: [Straiton, nearMotorwayRingRoad, Edinburgh City Bypass (A720)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearMotorwayRingRoad Context triple: [Straiton, nearMotorwayRingRoad, Edinburgh City Bypass (A720)]
-
A.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
B.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
C.
primaryRingRoad
Indicates that a road functions as the main circumferential or loop route encircling or bypassing a central area in a transport network.
-
D.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
E.
nearbyMajorRoad
chosen
Indicates that one entity is located close to a significant or heavily used road.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f423fdc9a48190a3e41e8dc2c5ad17 |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:55 a.m.