Triple

T20548503
Position Surface form Disambiguated ID Type / Status
Subject A32 Barrier Highway E504537 entity
Predicate routeNumber P1864 FINISHED
Object A32 NE NERFINISHED

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: A32 | Statement: [A32 Barrier Highway, routeNumber, A32]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A32
Context triple: [A32 Barrier Highway, routeNumber, A32]
  • A. A32 chosen
    A32 is an Australian state highway route designation assigned to the Mitchell Highway and associated connecting roads.
  • B. A33
    A33 is a major road in southern England that runs between Reading and Southampton, serving as an important regional transport route.
  • C. A232
    The A232 is a major road in the London Borough of Bromley that provides an important route for local and through traffic across South London.
  • D. A3220
    A3220 is a major road in West London that connects key routes between the Westway and the Chelsea area, serving as an important north–south urban artery.
  • E. A34
    A34 is a major trunk road in England that runs from Winchester in Hampshire to Salford near Manchester, serving as an important north–south transport route.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b52c048190952b4d0f430813a3 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5d56060819090f0e2f2f9957982 completed April 20, 2026, 10:16 p.m.
Created at: April 16, 2026, 11:38 a.m.