Triple

T21476883
Position Surface form Disambiguated ID Type / Status
Subject Buchan Ness E529884 entity
Predicate nearbySettlement P350 FINISHED
Object Boddam 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: Boddam | Statement: [Buchan Ness, nearbySettlement, Boddam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boddam
Context triple: [Buchan Ness, nearbySettlement, Boddam]
  • A. Boddam chosen
    Boddam is a coastal fishing village in Aberdeenshire, Scotland, known for its historic lighthouse and rugged North Sea shoreline.
  • B. Blatchford
    Blatchford is a sustainable, mixed-use residential community being developed on the former Edmonton City Centre Airport lands in Edmonton, Alberta.
  • C. Baldry
    Baldry is a small rural locality situated within the Cabonne Shire region of New South Wales, Australia.
  • D. Benthall
    Benthall is a small village in Shropshire, England, known for its historic Benthall Hall and rural surroundings near the town of Broseley.
  • E. Damsay
    Damsay is a small uninhabited island in the Orkney archipelago of Scotland, known for its low-lying terrain and archaeological remains.
  • 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_69e0c459acb481909bb6ee452a0045c7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea187a3c8190b3f33bd760dc1f54 completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:20 p.m.