Triple

T8028910
Position Surface form Disambiguated ID Type / Status
Subject Reginald Warneford E186926 entity
Predicate familyName P18 FINISHED
Object Warneford E186926 NE FINISHED

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: Warneford | Statement: [Reginald Warneford, familyName, Warneford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Warneford
Context triple: [Reginald Warneford, familyName, Warneford]
  • A. Warneford chosen
    Warneford is an English surname most notably associated with Reginald Warneford, a World War I flying ace and Victoria Cross recipient.
  • B. Holwell
    Holwell is a small rural village located within the North Hertfordshire district of Hertfordshire, England.
  • C. Wardle
    Wardle is a village in Greater Manchester, England, known for its moorland surroundings and historic textile industry roots.
  • D. Wangford
    Wangford is a small rural village and civil parish located in the English county of Suffolk.
  • E. Holywell
    Holywell is a historic market town in northeast Wales renowned for St Winefride's Well, a major medieval pilgrimage site often called the "Lourdes of Wales."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca82ad4e2c8190a693e3c9e30fe66f completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3ecdbc5881909246982b93978841 completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc56e146048190a97b3b37d1eec0b8 completed March 31, 2026, 11:21 p.m.
Created at: March 30, 2026, 5:21 p.m.