Triple
T831841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M23 motorway |
E17981
|
entity |
| Predicate | hasJunctionNumbering |
P20130
|
FINISHED |
| Object | Junctions 7 to 11 |
—
|
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: Junctions 7 to 11 | Statement: [M23 motorway, hasJunctionNumbering, Junctions 7 to 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJunctionNumbering Context triple: [M23 motorway, hasJunctionNumbering, Junctions 7 to 11]
-
A.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
B.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
C.
boroughNumber
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
D.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
E.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab60fea8819098ce3269181897d1 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.