Triple

T14900986
Position Surface form Disambiguated ID Type / Status
Subject M60 motorway E360001 entity
Predicate hasJunction P1018 FINISHED
Object Junction 11
Junction 11 is an interchange on the M60 motorway in Greater Manchester, England, providing access between the orbital route and local roads.
 E1129409 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 11 | Statement: [M60 motorway, hasJunction, Junction 11]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Junction 11
Context triple: [M60 motorway, hasJunction, Junction 11]
  • A. Junction 1
    Junction 1 is a major road interchange on England’s M58 motorway, connecting it with local and regional routes.
  • B. Junction 1
    Junction 1 is a motorway interchange on the M20 in southeast England, providing access between the M20 and local roads near the London orbital route.
  • C. Junction 1
    Junction 1 is a key interchange on the M60 motorway near Stockport, connecting local roads to the orbital route around Greater Manchester.
  • D. Junction 7
    Junction 7 is a numbered interchange on the M20 motorway in England, providing access between the motorway and the surrounding local road network.
  • E. Junction 7
    Junction 7 is a numbered junction on England’s M58 motorway, serving as one of the route’s access and exit points.
  • 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 11
Triple: [M60 motorway, hasJunction, Junction 11]
Generated description
Junction 11 is an interchange on the M60 motorway in Greater Manchester, England, providing access between the orbital route and local roads.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Junction 11
Target entity description: Junction 11 is an interchange on the M60 motorway in Greater Manchester, England, providing access between the orbital route and local roads.
  • A. Junction 1
    Junction 1 is a major road interchange on England’s M58 motorway, connecting it with local and regional routes.
  • B. Junction 1
    Junction 1 is a motorway interchange on the M20 in southeast England, providing access between the M20 and local roads near the London orbital route.
  • C. Junction 1
    Junction 1 is a key interchange on the M60 motorway near Stockport, connecting local roads to the orbital route around Greater Manchester.
  • D. Junction 7
    Junction 7 is a numbered interchange on the M20 motorway in England, providing access between the motorway and the surrounding local road network.
  • E. Junction 7
    Junction 7 is a numbered junction on England’s M58 motorway, serving as one of the route’s access and exit points.
  • F. None of above. chosen

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_69fe8bcf32a48190b1f036016f2689b7 completed May 9, 2026, 1:20 a.m.
NEDg Description generation batch_69fe8d68bbec8190a60233dc22bcb69f completed May 9, 2026, 1:27 a.m.
NED2 Entity disambiguation (via description) batch_69fe8e8f0c588190a91c1fca25708a05 completed May 9, 2026, 1:31 a.m.
Created at: April 10, 2026, 2:11 a.m.