Triple

T14461992
Position Surface form Disambiguated ID Type / Status
Subject Lydney Harbour E358603 entity
Predicate nearbySettlement P350 FINISHED
Object Lydney town E72705 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: Lydney town | Statement: [Lydney Harbour, nearbySettlement, Lydney town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lydney town
Context triple: [Lydney Harbour, nearbySettlement, Lydney town]
  • A. Lydney chosen
    Lydney is a small town in southwest England situated on the River Severn near the Forest of Dean.
  • B. Littondale
    Littondale is a scenic side valley of the Yorkshire Dales in North Yorkshire, England, known for its traditional villages, limestone scenery, and tranquil rural character.
  • C. Elmdon
    Elmdon is a village and former civil parish in the West Midlands of England, historically notable as the original site of what is now Birmingham Airport (formerly Elmdon Airport).
  • D. Ashton Vale
    Ashton Vale is a residential and industrial suburb on the southwestern edge of Bristol, England.
  • E. Hellingly
    Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91abc1008190a19de4f8f0112c9d completed April 14, 2026, 7:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8aa904c08190b33796b832aa100f completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:19 a.m.