Triple

T19820018
Position Surface form Disambiguated ID Type / Status
Subject Oldcotes Dyke E476163 entity
Predicate flowsThrough P225 FINISHED
Object Langold 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: Langold | Statement: [Oldcotes Dyke, flowsThrough, Langold]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langold
Context triple: [Oldcotes Dyke, flowsThrough, Langold]
  • A. Langold chosen
    Langold is a village in Nottinghamshire, England, known for its former mining community and nearby Langold Country Park.
  • B. Grimston
    Grimston is a village and civil parish in the English county of Norfolk, known for its historic church and rural setting near King’s Lynn.
  • C. Balderstone
    Balderstone is a district and residential area within the Balderstone and Kirkholt ward of Rochdale in Greater Manchester, England.
  • D. Hawise
    Hawise is a medieval European female given name borne by several noblewomen in England and France.
  • E. Grosmont
    Grosmont is a small village in North Yorkshire, England, known for its heritage railway station on the North Yorkshire Moors Railway and its scenic moorland surroundings.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654fe0ff8819084bad251b76eff77 completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.