Triple

T21804329
Position Surface form Disambiguated ID Type / Status
Subject M4 corridor E538311 entity
Predicate hasPart P35 FINISHED
Object Newbury 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: Newbury | Statement: [M4 corridor, hasPart, Newbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newbury
Context triple: [M4 corridor, hasPart, Newbury]
  • A. Newbury
    Newbury is a small rural community located in southwestern Ontario, Canada.
  • B. Newbury, Berkshire chosen
    Newbury, Berkshire is a historic market town in southern England known for its racecourse, proximity to Highclere Castle, and role as a commercial and administrative center in West Berkshire.
  • C. Woburn
    Woburn is a residential neighbourhood in the eastern part of Toronto, Ontario, known for its diverse community and mix of high-rise apartments and single-family homes.
  • D. Woburn
    Woburn is a village in Saint George Parish on the Caribbean island nation of Grenada.
  • E. Woburn
    Woburn is a residential suburb of Lower Hutt in the Wellington region of New Zealand, known for its leafy streets and established homes.
  • 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07801fa8081909098d00947bf8f7f completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.