Triple

T21127534
Position Surface form Disambiguated ID Type / Status
Subject Battle of Edington E520596 entity
Predicate locatedIn P40 FINISHED
Object Edington 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: Edington | Statement: [Battle of Edington, locatedIn, Edington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edington
Context triple: [Battle of Edington, locatedIn, Edington]
  • A. Edington chosen
    Edington is a village in Wiltshire, England, historically notable as the site of King Alfred the Great’s decisive victory over Viking forces in 878 AD.
  • B. Southwold
    Southwold is a small seaside town and popular tourist resort on the North Sea coast of Suffolk, England, known for its pier, beach huts, and historic lighthouse.
  • C. Southwold
    Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
  • D. Upington
    Upington is a town in South Africa’s Northern Cape province, serving as a key regional center on the Orange River and a gateway to nearby desert and wildlife attractions.
  • E. Alvediston
    Alvediston is a small rural village in Wiltshire, England, known for its historic manor house and picturesque countryside setting.
  • 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_69e0b50a623881909c0bbaf4f2c055e7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72239965c819081b4077b914d0a98 completed April 21, 2026, 7:07 a.m.
Created at: April 16, 2026, 2:56 p.m.