Triple
T37387734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tingley Interchange |
E928616
|
entity |
| Predicate | junctionNumberOnM1 |
P43890
|
FINISHED |
| Object | 42 |
—
|
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: 42 | Statement: [Tingley Interchange, junctionNumberOnM1, 42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: junctionNumberOnM1 Context triple: [Tingley Interchange, junctionNumberOnM1, 42]
-
A.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or system.
-
B.
nextJunctionOnM1
Indicates that one junction is the immediate subsequent junction along the M1 route from another junction.
-
C.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
-
D.
hasJunctionNumberOnM60
Indicates that an entity has a specific junction number assigned on the M60 motorway.
-
E.
hasJunctionNumber
chosen
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.