Triple
T3702269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junction 11 of M60 motorway |
E80805
|
entity |
| Predicate | hasJunctionType |
P49487
|
FINISHED |
| Object | grade-separated interchange |
—
|
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: grade-separated interchange | Statement: [Junction 11 of M60 motorway, hasJunctionType, grade-separated interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJunctionType Context triple: [Junction 11 of M60 motorway, hasJunctionType, grade-separated interchange]
-
A.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
hasJunctionIn
Indicates that one entity contains or includes a junction located within the spatial or structural extent of another entity.
-
C.
hasJunctionNumber
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
-
D.
hasJointType
Indicates that one entity is associated with, or characterized by, a specific type or category of joint.
-
E.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54925b48190b23d2a14ef825abc |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb903be308190a8f1925f99e67c68 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:33 p.m.