Triple

T6170842
Position Surface form Disambiguated ID Type / Status
Subject church ruins at Cullingsburgh E137691 entity
Predicate location P40 FINISHED
Object Cullingsburgh E169973 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: Cullingsburgh | Statement: [church ruins at Cullingsburgh, location, Cullingsburgh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cullingsburgh
Context triple: [church ruins at Cullingsburgh, location, Cullingsburgh]
  • A. Cullingsburgh chosen
    Cullingsburgh is a small settlement on the island of Bressay in the Shetland Islands of Scotland.
  • B. Winchburgh
    Winchburgh is a rapidly growing village in West Lothian, Scotland, known for its major housing and infrastructure expansion projects transforming it into a new town.
  • C. Strensall
    Strensall is a village and civil parish in North Yorkshire, England, known for its nearby military training area and nature reserve.
  • D. Coldingham
    Coldingham is a historic coastal village in the Scottish Borders, known for its ancient priory and nearby Coldingham Bay.
  • E. Dunnichen
    Dunnichen is a small rural village in eastern Scotland, historically noted as a possible site of the Battle of Dunnichen (Nechtansmere) in 685 AD.
  • 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_69c008a68c508190a8d78245c865960e completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d910c3c8190ae6af548259295ff completed March 22, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c141ad559881909076b6ab34b14f2b completed March 23, 2026, 1:35 p.m.
Created at: March 22, 2026, 4:18 p.m.