Triple

T17430446
Position Surface form Disambiguated ID Type / Status
Subject Aston, Cote, Shifford and Chimney E423854 entity
Predicate containsSettlement P847 FINISHED
Object Aston 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: Aston | Statement: [Aston, Cote, Shifford and Chimney, containsSettlement, Aston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aston
Context triple: [Aston, Cote, Shifford and Chimney, containsSettlement, Aston]
  • A. Aston
    Aston is a masculine given name of English origin, used both as a first name and a surname.
  • B. Aston chosen
    Aston is a small rural village located within the district of West Oxfordshire in Oxfordshire, England.
  • C. Aston, Birmingham
    Aston, Birmingham is an inner-city district of Birmingham, England, known for its rich industrial history, diverse community, and association with the Aston Villa Football Club.
  • D. Leyland
    Leyland is a town in Lancashire, England, historically known for its vehicle manufacturing industry, particularly Leyland Motors.
  • E. Chandlers Ford
    Chandlers Ford is a suburban town in Hampshire, England, situated between Southampton and Winchester and known primarily as a residential and commuter area.
  • 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e448ffb9c8819099fabfeebdc06883 completed April 19, 2026, 3:16 a.m.
Created at: April 10, 2026, 5:46 a.m.