Triple
T34574471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dun, Angus |
E887712
|
entity |
| Predicate | hasEcclesiasticalAssociation |
P13041
|
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: [Dun, Angus, hasEcclesiasticalAssociation, Church of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcclesiasticalAssociation Context triple: [Dun, Angus, hasEcclesiasticalAssociation, Church of Scotland]
-
A.
hasEcclesialIdentity
Indicates that an entity possesses or is characterized by a particular ecclesial (church-related) identity or affiliation.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
ecclesialRelationship
Indicates a formal relationship or connection between entities within a church or ecclesiastical structure.
-
D.
associatedWithChurch
chosen
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
E.
isEcclesiasticalFormOf
Indicates that one term is the ecclesiastical (church-related or liturgical) form or variant of another term.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7209895288190ae44354012537e8e |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.