Triple

T23384351
Position Surface form Disambiguated ID Type / Status
Subject Clun Castle E593835 entity
Predicate locatedIn P40 FINISHED
Object Clun 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: Clun | Statement: [Clun Castle, locatedIn, Clun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clun
Context triple: [Clun Castle, locatedIn, Clun]
  • A. Clun chosen
    Clun is a small historic village in the Shropshire Hills of England, known for its medieval castle ruins and picturesque rural setting.
  • B. Clun Forest
    Clun Forest is a remote, sparsely populated upland area in southwest Shropshire, England, known for its rolling hills, ancient woodlands, and traditional sheep farming.
  • C. Clunia
    Clunia was an important Roman city in Hispania known as a political and administrative center and for its extensive archaeological remains, including a large theater and forum.
  • D. Clunie
    Clunie is a small village in Perth and Kinross, Scotland, known for its historic parish church and scenic rural surroundings.
  • E. Drigg
    Drigg is a coastal village in Cumbria, England, known for its sandy beaches, dunes, and proximity to the Lake District.
  • 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a497661c8190b52fa27419594989 completed April 29, 2026, 6:26 a.m.
Created at: April 17, 2026, 5:34 p.m.