Triple
T2998836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgend Designer Outlet |
E81135
|
entity |
| Predicate | nearbyJunction |
P16027
|
FINISHED |
| Object | M4 Junction 36 |
—
|
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: M4 Junction 36 | Statement: [Bridgend Designer Outlet, nearbyJunction, M4 Junction 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyJunction Context triple: [Bridgend Designer Outlet, nearbyJunction, M4 Junction 36]
-
A.
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.
-
B.
motorwayJunctionNearby
chosen
Indicates that a motorway junction is located close to the referenced entity.
-
C.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
D.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.