Triple

T22140547
Position Surface form Disambiguated ID Type / Status
Subject Canberra Central E547144 entity
Predicate contains P35 FINISHED
Object Lyneham 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: Lyneham | Statement: [Canberra Central, contains, Lyneham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lyneham
Context triple: [Canberra Central, contains, Lyneham]
  • A. Lyneham chosen
    Lyneham is a residential suburb in Canberra, Australia, known for its tree-lined streets, sporting facilities, and proximity to the city centre.
  • B. Lyneham
    Lyneham is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
  • C. Kempshott
    Kempshott is a residential suburb of Basingstoke in Hampshire, England, known for its family housing and local amenities.
  • D. Mileham
    Mileham is a small rural village and civil parish in Norfolk, England, known for its historic church and remains of a Norman motte-and-bailey castle.
  • E. Pavenham
    Pavenham is a rural village and civil parish in Bedfordshire, England, known for its historic church, traditional English countryside setting, and community-focused village life.
  • 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129bda1208190b851ae5c68b760e9 completed April 28, 2026, 9:42 p.m.
Created at: April 16, 2026, 8:32 p.m.