Triple

T13949129
Position Surface form Disambiguated ID Type / Status
Subject River Gade E335471 entity
Predicate flowsThrough P225 FINISHED
Object Kings Langley E215268 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: Kings Langley | Statement: [River Gade, flowsThrough, Kings Langley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kings Langley
Context triple: [River Gade, flowsThrough, Kings Langley]
  • A. Kings Langley chosen
    Kings Langley is a historic village and civil parish in southern England, situated northwest of London and known for its medieval royal connections.
  • B. Abbots Langley
    Abbots Langley is a large historic village and civil parish in the county of Hertfordshire in southern England.
  • C. Berkhamsted
    Berkhamsted is a historic market town in Hertfordshire, England, known for its medieval castle remains and role as a commuter hub northwest of London.
  • D. Langley, Kent
    Langley, Kent is a small village and civil parish in the Maidstone district of Kent, England, known for its rural character and historic parish church.
  • E. Abingdon
    Abingdon is a historic market town in Oxfordshire, England, often claimed to be one of the oldest continuously inhabited towns in the country.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e12171c8190b95746bdd4845def completed April 14, 2026, 12:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7ce917b7881908e1916fe2c597fe4 completed May 3, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:17 p.m.