Triple

T10088006
Position Surface form Disambiguated ID Type / Status
Subject Kings Langley E215268 entity
Predicate hasHistoricalName P2834 FINISHED
Object Langley Regis E351659 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: Langley Regis | Statement: [Kings Langley, hasHistoricalName, Langley Regis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langley Regis
Context triple: [Kings Langley, hasHistoricalName, Langley Regis]
  • A. Orsett
    Orsett is a village and civil parish in the borough of Thurrock in Essex, England, known for its historic church and traditional village green.
  • B. Wooburn Green
    Wooburn Green is a village and large green in Buckinghamshire, England, situated near High Wycombe in the River Wye valley.
  • C. Datchet
    Datchet is a riverside village and civil parish in Berkshire, England, situated on the River Thames near Windsor.
  • D. Codicote chosen
    Codicote is a village and civil parish in the county of Hertfordshire in southern England.
  • E. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • 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_69ca83a1eed081908b2e9580f2ebeea7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd04875748190a81d1e9ad68dda96 completed April 2, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b693afac819090635d2eb147bdcb completed April 5, 2026, 7:22 p.m.
Created at: March 30, 2026, 9:01 p.m.