Triple
T35204433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford Gap |
E1016494
|
entity |
| Predicate | hasRoadJunctionNearby |
P31669
|
FINISHED |
| Object | M1 junction 17 |
—
|
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: M1 junction 17 | Statement: [Watford Gap, hasRoadJunctionNearby, M1 junction 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadJunctionNearby Context triple: [Watford Gap, hasRoadJunctionNearby, M1 junction 17]
-
A.
nearJunctionOf
chosen
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.
hasRoadJunctionType
Indicates that a road junction has a specific type or classification (e.g., roundabout, intersection, interchange).
-
C.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
E.
atJunctionOf
Indicates that something is located at or directly connected to the point where two or more paths, roads, or lines meet.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:02 p.m.