Triple

T26031309
Position Surface form Disambiguated ID Type / Status
Subject Closeburn, Dumfriesshire E647436 entity
Predicate historicalParishIn P101108 FINISHED
Object Church of Scotland 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: Church of Scotland | Statement: [Closeburn, Dumfriesshire, historicalParishIn, Church of Scotland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalParishIn
Context triple: [Closeburn, Dumfriesshire, historicalParishIn, Church of Scotland]
  • A. isHistoricParishOf chosen
    Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
  • B. hasParishHistory
    Indicates that an entity possesses or is associated with a documented historical record of a parish.
  • C. hasHistoricParishCharacter
    Indicates that something possesses the distinctive qualities or attributes traditionally associated with a historic parish.
  • D. historicalTownshipOf
    Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
  • E. civilParishIn
    Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
  • F. None of above.

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_69e77e8b60e88190a3b26c4f0032a2c2 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: April 22, 2026, 9:06 a.m.