Triple
T26155891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junction 32 of the M4 motorway |
E659958
|
entity |
| Predicate | roadJunctionNumber |
P43890
|
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: [Junction 32 of the M4 motorway, roadJunctionNumber, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadJunctionNumber Context triple: [Junction 32 of the M4 motorway, roadJunctionNumber, 32]
-
A.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
B.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
C.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
-
D.
hasJunctionNumber
chosen
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0fd6a08190bafd573b07bb2fe8 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:27 p.m.