Triple

T17029192
Position Surface form Disambiguated ID Type / Status
Subject Hillsborough E413144 entity
Predicate locatedNear P294 FINISHED
Object M1 motorway E86446 NE 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: M1 motorway | Statement: [Hillsborough, locatedNear, M1 motorway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M1 motorway
Context triple: [Hillsborough, locatedNear, M1 motorway]
  • A. M1 motorway chosen
    The M1 motorway is a major north–south highway in England linking London with key cities in the Midlands and northern England.
  • B. M1 motorway
    The M1 motorway is a major Hungarian highway that connects Budapest with the western regions of the country and continues toward the Austrian border.
  • C. M1 motorway
    The M1 motorway is a major north–south highway in Johannesburg, South Africa, forming part of the city’s primary arterial road network.
  • D. M1 motorway
    The M1 motorway is a major Hungarian highway connecting Budapest with the northwestern city of Győr and the Austrian border, forming part of the main route between Hungary and Western Europe.
  • E. M1 motorway
    The M1 motorway is a major Hungarian highway that connects Budapest with the northwestern border near Austria, forming part of a key international transport corridor.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d5d858448190acfe81f10d83ed4b completed April 18, 2026, 7:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a01232149f88190b385fca6a7588d7b completed May 11, 2026, 12:30 a.m.
Created at: April 10, 2026, 5:33 a.m.