Triple
T26322489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coryton Interchange |
E662150
|
entity |
| Predicate | roadJunctionNumberOnM4 |
P160245
|
FINISHED |
| Object | 32 |
—
|
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: 32 | Statement: [Coryton Interchange, roadJunctionNumberOnM4, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadJunctionNumberOnM4 Context triple: [Coryton Interchange, roadJunctionNumberOnM4, 32]
-
A.
hasJunctionNumberOnM60
Indicates that an entity has a specific junction number assigned on the M60 motorway.
-
B.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
C.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
D.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
E.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f2cf8148190acaf42480d5abf0e |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:29 p.m.