Triple

T17920415
Position Surface form Disambiguated ID Type / Status
Subject North West London E448050 entity
Predicate hasMajorRoad P385 FINISHED
Object A41 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: A41 | Statement: [North West London, hasMajorRoad, A41]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A41
Context triple: [North West London, hasMajorRoad, A41]
  • A. A41 chosen
    The A41 is a major road in England that runs between London and Birkenhead, serving as an important route through the Midlands and Home Counties.
  • B. A414
    The A414 is a major east–west road in southern England that links several Hertfordshire towns and provides an important route near Welwyn Garden City.
  • C. A417
    A417 is a major road in England that links key towns and routes in Gloucestershire and the surrounding region.
  • D. A418
    The A418 is a primary road in England that connects the town of Thame with other nearby settlements and major routes in the region.
  • E. A419
    The A419 is a major road in England that links Swindon with Gloucester, serving as an important regional route in the southwest.
  • 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_69d8b9f6d394819082a6d69fd1e23d2f completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a309532881908633bd723923880f completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 10:20 a.m.