Triple

T13335080
Position Surface form Disambiguated ID Type / Status
Subject UB7 E317667 entity
Predicate covers P1393 FINISHED
Object Harmondsworth 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: Harmondsworth | Statement: [UB7, covers, Harmondsworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harmondsworth
Context triple: [UB7, covers, Harmondsworth]
  • A. Harmondsworth chosen
    Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
  • B. Hendon
    Hendon is an English surname most notably associated with the fictional character Miles Hendon from Mark Twain’s novel "The Prince and the Pauper."
  • C. Hendon
    Hendon is a district of Sunderland in Tyne and Wear, England, known historically for its shipbuilding and industrial heritage.
  • D. Hendon
    Hendon is a suburban district in the London Borough of Barnet, historically known for its aerodrome and role in early British aviation.
  • E. Rickmansworth
    Rickmansworth is a small town in south-west Hertfordshire, England, known for its canals, lakes, and role as a commuter suburb of London.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cff44e08190b9583baf0b626e42 completed April 11, 2026, 12:59 a.m.
Created at: April 9, 2026, 9:30 p.m.