Triple
T10602753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leigh Delamere services |
E275790
|
entity |
| Predicate | roadJunctionProximity |
P16027
|
FINISHED |
| Object | between junction 17 and junction 18 of the M4 |
—
|
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: between junction 17 and junction 18 of the M4 | Statement: [Leigh Delamere services, roadJunctionProximity, between junction 17 and junction 18 of the M4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadJunctionProximity Context triple: [Leigh Delamere services, roadJunctionProximity, between junction 17 and junction 18 of the M4]
-
A.
motorwayJunctionNearby
chosen
Indicates that a motorway junction is located close to the referenced entity.
-
B.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
C.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
D.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
E.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:31 p.m.