Triple

T15694642
Position Surface form Disambiguated ID Type / Status
Subject Calder Valley ward E380426 entity
Predicate contains P35 FINISHED
Object Luddendenfoot E17988 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: Luddendenfoot | Statement: [Calder Valley ward, contains, Luddendenfoot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luddendenfoot
Context triple: [Calder Valley ward, contains, 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. Saundersfoot
    Saundersfoot is a coastal village and popular seaside resort in southwest Wales known for its sandy beach and picturesque harbour.
  • C. Dumbreck
    Dumbreck is a railway station in Glasgow, Scotland, serving the Dumbreck area on the suburban network.
  • D. 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.
  • E. Niddrie
    Niddrie is a residential district in the southeast of Edinburgh, Scotland, historically associated with working-class housing and post-war redevelopment.
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f50ce848190a839c4fb7306d793 completed April 16, 2026, 2:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6eed9a8c8190a57ffce61a27ec17 completed May 9, 2026, 5:29 p.m.
Created at: April 10, 2026, 4:44 a.m.