Triple

T15278728
Position Surface form Disambiguated ID Type / Status
Subject Killingworth Lake E365210 entity
Predicate locatedIn P40 FINISHED
Object Killingworth E71801 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: Killingworth | Statement: [Killingworth Lake, locatedIn, Killingworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Killingworth
Context triple: [Killingworth Lake, locatedIn, Killingworth]
  • A. Killingworth chosen
    Killingworth is a village in North Tyneside, England, historically notable for its early coal mining and railway engineering associations.
  • B. Crosthwaite
    Crosthwaite is a small village in England’s Lake District, known for its rural charm and scenic surroundings.
  • C. Winford
    Winford is a small village and civil parish in North Somerset, England, situated near Bristol Airport and known for its rural character.
  • D. Woodcroft
    Woodcroft is a suburban residential area located within the City of Onkaparinga in the southern region of Adelaide, South Australia.
  • E. Whitewell
    Whitewell is a small rural hamlet in Lancashire, England, known for its scenic setting in the Forest of Bowland and traditional stone buildings.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00e504d8c8190ad6c565a31d1a9bd completed April 15, 2026, 10:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef754c9c8190abdc1d08fd1511cd completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:14 a.m.