Triple

T1602726
Position Surface form Disambiguated ID Type / Status
Subject Horwich Works E34431 entity
Predicate locatedIn P40 FINISHED
Object Horwich E35592 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: Horwich | Statement: [Horwich Works, locatedIn, Horwich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horwich
Context triple: [Horwich Works, locatedIn, Horwich]
  • A. Horwich chosen
    Horwich is a town in Greater Manchester, England, historically notable as a major railway engineering and locomotive works centre.
  • B. Killingworth
    Killingworth is a village in North Tyneside, England, historically notable for its early coal mining and railway engineering associations.
  • C. Hawarden
    Hawarden is a village in Flintshire, Wales, historically notable as the longtime home and final residence of British Prime Minister William Ewart Gladstone.
  • D. Corringham
    Corringham is a small town and civil parish in the unitary authority of Thurrock in Essex, England, with historic roots and a largely residential character.
  • E. Owerton
    Owerton is an alternative spelling of the name Overton, which is used for various places and surnames in English-speaking regions.
  • 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa62292d1c819080b597199dc6b8d5 completed March 6, 2026, 5:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad46ad15b081908b59df18224c7a8f completed March 8, 2026, 9:51 a.m.
Created at: March 4, 2026, 7:28 p.m.