Triple

T18104568
Position Surface form Disambiguated ID Type / Status
Subject Luddenden Brook E433314 entity
Predicate mouthLocation P417 FINISHED
Object Luddendenfoot 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: Luddendenfoot | Statement: [Luddenden Brook, mouthLocation, Luddendenfoot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luddendenfoot
Context triple: [Luddenden Brook, mouthLocation, Luddendenfoot]
  • A. Luddenden Foot chosen
    Luddenden Foot is a village in Calderdale, West Yorkshire, England, situated in the Upper Calder Valley and historically associated with textile manufacturing and canal-side industry.
  • B. Longden
    Longden is an English-language surname borne by various notable individuals across fields such as politics, sports, and the arts.
  • C. Saundersfoot
    Saundersfoot is a coastal village and popular seaside resort in southwest Wales known for its sandy beach and picturesque harbour.
  • D. Dumbreck
    Dumbreck is a railway station in Glasgow, Scotland, serving the Dumbreck area on the suburban network.
  • E. Laurieston
    Laurieston is a district in Glasgow, Scotland, known for its central location near the River Clyde and mix of residential and urban redevelopment areas.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddb8dd308190a9c98ac2b1d8b872 completed April 19, 2026, 1:50 p.m.
Created at: April 10, 2026, 10:28 a.m.