Triple

T13772033
Position Surface form Disambiguated ID Type / Status
Subject Wharfedale E330903 entity
Predicate containsSettlement P847 FINISHED
Object Addingham E929121 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: Addingham | Statement: [Wharfedale, containsSettlement, Addingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Addingham
Context triple: [Wharfedale, containsSettlement, Addingham]
  • A. Addingham chosen
    Addingham is a picturesque village in West Yorkshire, England, situated between Ilkley and Skipton on the River Wharfe.
  • B. Glendinning
    Glendinning is a small rural locality in Dumfries and Galloway, Scotland, known as the birthplace of the renowned civil engineer Thomas Telford.
  • C. Croftamie
    Croftamie is a small rural village in central Scotland, situated within the Stirling council area and known for its scenic countryside setting.
  • D. Colliston
    Colliston is a small rural village located within the Angus council area in eastern Scotland.
  • E. Coningham
    Coningham is an English-language surname borne by several notable figures, including military officers and politicians.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0235aea881909ab4c721db081b00 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a86907cc8190a6a6b475d08f0dc7 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:10 p.m.