Triple
T27445821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M8 motorway |
E692274
|
entity |
| Predicate | hasHardShoulder |
P67768
|
FINISHED |
| Object | yes on most sections |
—
|
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: yes on most sections | Statement: [M8 motorway, hasHardShoulder, yes on most sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHardShoulder Context triple: [M8 motorway, hasHardShoulder, yes on most sections]
-
A.
hasEmergencyLane
chosen
Indicates that a road, route, or similar thoroughfare includes a designated emergency lane for use by emergency or breakdown situations.
-
B.
hasCarriagewayFacilities
Indicates that specific facilities, features, or infrastructure elements are present on or along a carriageway.
-
C.
hasRoadWidth
Indicates the width measurement of a road segment or roadway in the relationship.
-
D.
hasCarriagewayType
Indicates the specific structural or functional type of carriageway associated with a road segment (e.g., single, dual, or other carriageway configurations).
-
E.
hasSlipRoads
Indicates that a road segment is connected to one or more slip roads (on-ramps or off-ramps) providing access to or from it.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 12:46 p.m.