Triple

T15119210
Position Surface form Disambiguated ID Type / Status
Subject Metropolitan Borough of Dudley E361122 entity
Predicate contains P35 FINISHED
Object Wordsley E813918 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: Wordsley | Statement: [Metropolitan Borough of Dudley, contains, Wordsley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wordsley
Context triple: [Metropolitan Borough of Dudley, contains, Wordsley]
  • A. Wordsley chosen
    Wordsley is a suburban village in the West Midlands of England, situated near the town of Stourbridge and historically associated with the region’s glassmaking industry.
  • B. Thorley
    Thorley is a village and civil parish in Hertfordshire, England, situated just southwest of the town of Bishop's Stortford.
  • C. Willaston
    Willaston is a village in Cheshire, England, situated near the town of Crewe.
  • D. Rowsley
    Rowsley is a village in Derbyshire, England, known for its scenic location near the Peak District and its historic railway and riverside setting.
  • E. Elsecar
    Elsecar is a village in South Yorkshire, England, known for its industrial heritage and preserved railway connections.
  • 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_69d85a0491ec8190830960be8fafb994 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0059e036c8190959ff3bde8f2356f completed April 15, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7f2e3408190ae095d16396e420d completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 3:06 a.m.