Triple

T14307346
Position Surface form Disambiguated ID Type / Status
Subject Minto railway station E354731 entity
Predicate formerName P65 FINISHED
Object Minto Road E790109 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: Minto Road | Statement: [Minto railway station, formerName, Minto Road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minto Road
Context triple: [Minto railway station, formerName, Minto Road]
  • A. Minto Road chosen
    Minto Road is a major thoroughfare in New Delhi that connects key government, commercial, and transport hubs in the heart of the city.
  • B. Minto Street
    Minto Street is a main thoroughfare in Edinburgh, Scotland, known for its traditional tenement buildings, guesthouses, and proximity to the city centre.
  • C. Bunder Road
    Bunder Road is the former name of a major historic thoroughfare in Karachi, Pakistan, now known as M.A. Jinnah Road.
  • D. Lamington Road
    Lamington Road is a local roadway serving the village of Lamington, providing access and connectivity within this rural community.
  • E. Lane Cove Road
    Lane Cove Road is a major arterial route in Sydney’s northern suburbs that links several residential and commercial areas and connects to key regional roads.
  • 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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de85b156b0819083f2bd319deed1b6 completed April 14, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdd5be63848190aa71f009ceaea1b3 completed May 8, 2026, 12:23 p.m.
Created at: April 10, 2026, 1:12 a.m.