Triple
T30441051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 Junction 19 |
E774443
|
entity |
| Predicate | previousJunctionOnM6 |
P195727
|
FINISHED |
| Object | M6 Junction 1 |
—
|
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: M6 Junction 1 | Statement: [M1 Junction 19, previousJunctionOnM6, M6 Junction 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousJunctionOnM6 Context triple: [M1 Junction 19, previousJunctionOnM6, M6 Junction 1]
-
A.
previousJunctionOnM1
Indicates that one junction is the immediately preceding junction to another along the M1 motorway.
-
B.
nextJunctionOnM1
Indicates that one junction is the immediate subsequent junction along the M1 route from another junction.
-
C.
roadJunctionNumberOnM4
Indicates the specific junction number that a road has on the M4 motorway.
-
D.
hasJunctionNumberOnM60
Indicates that an entity has a specific junction number assigned on the M60 motorway.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 29, 2026, 8:08 p.m.