Triple
T14901005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M60 motorway |
E360001
|
entity |
| Predicate | hasJunction |
P1018
|
FINISHED |
| Object |
Junction 4a
Junction 4a is a numbered interchange on the M60 motorway in Greater Manchester, connecting local roads to the orbital route around Manchester.
|
E1126969
|
NE FINISHED |
How this triple was built (4 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: Junction 4a | Statement: [M60 motorway, hasJunction, Junction 4a]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Junction 4a Context triple: [M60 motorway, hasJunction, Junction 4a]
-
A.
Junction 3a
Junction 3a is a numbered interchange on the M60 motorway in Greater Manchester, England, providing access between the orbital route and local roads.
-
B.
Junction 4
Junction 4 is a junction on England’s M55 motorway, serving as one of the key access points between the motorway and the local road network near Blackpool.
-
C.
Junction 4
Junction 4 is an interchange on the M60 motorway in Greater Manchester, England, connecting the orbital route with local roads and nearby urban areas.
-
D.
Junction 6
Junction 6 is an interchange on England’s M58 motorway connecting local roads to the regional motorway network.
-
E.
Junction
Junction was the former name of the city now known as Englewood in Montgomery County, Ohio.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Junction 4a Triple: [M60 motorway, hasJunction, Junction 4a]
Generated description
Junction 4a is a numbered interchange on the M60 motorway in Greater Manchester, connecting local roads to the orbital route around Manchester.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Junction 4a Target entity description: Junction 4a is a numbered interchange on the M60 motorway in Greater Manchester, connecting local roads to the orbital route around Manchester.
-
A.
Junction 3a
Junction 3a is a numbered interchange on the M60 motorway in Greater Manchester, England, providing access between the orbital route and local roads.
-
B.
Junction 4
Junction 4 is a junction on England’s M55 motorway, serving as one of the key access points between the motorway and the local road network near Blackpool.
-
C.
Junction 4
chosen
Junction 4 is an interchange on the M60 motorway in Greater Manchester, England, connecting the orbital route with local roads and nearby urban areas.
-
D.
Junction 6
Junction 6 is an interchange on England’s M58 motorway connecting local roads to the regional motorway network.
-
E.
Junction
Junction was the former name of the city now known as Englewood in Montgomery County, Ohio.
- F. None of above.
Provenance (5 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded609bf68819099ca3aa3fe1acadc |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e83418081908280a9ed8ddb9fd7 |
completed | May 9, 2026, 12:23 a.m. |
| NEDg | Description generation | batch_69fe7f9ea5848190af5edd6d2d22c117 |
completed | May 9, 2026, 12:28 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe7ff91dec8190aa9f0d42a8cd00e0 |
completed | May 9, 2026, 12:29 a.m. |
Created at: April 10, 2026, 2:11 a.m.