Triple

T14194283
Position Surface form Disambiguated ID Type / Status
Subject Westhoughton E351792 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Wingates E520754 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: Wingates | Statement: [Westhoughton, hasNeighbourhood, Wingates]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wingates
Context triple: [Westhoughton, hasNeighbourhood, Wingates]
  • A. Wingates chosen
    Wingates is a suburban area within the town of Westhoughton in Greater Manchester, England.
  • B. Wingate
    Wingate is a surname most notably associated with Orde Charles Wingate, an unconventional and influential British Army officer of the early 20th century.
  • C. Welch
    Welch is a small city in southern West Virginia known historically as a coal-mining community and the county seat of McDowell County.
  • D. Welch
    Welch is a surname of English origin borne by various notable individuals across fields such as entertainment, science, and politics.
  • E. WINGO
    WINGO is the radio callsign used by Wingo, a low-cost Colombian airline operating domestic and international flights in Latin America.
  • 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_69d827894ac0819097803e57f3227b23 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61e1fbd48190a4864fa4443f8f29 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd194951d481909a8e81f2d09feefa completed May 7, 2026, 10:59 p.m.
Created at: April 10, 2026, 1:04 a.m.