Triple
T29257647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | diocesan council of Roskilde |
E741746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representative church body |
C53601
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: representative church body Context triple: [diocesan council of Roskilde, instanceOf, representative church body]
-
A.
representative church council
chosen
A representative church council is a governing body composed of elected or appointed delegates from various congregations or church units that meets to deliberate, decide, and provide guidance on matters of doctrine, policy, and administration for the wider church.
-
B.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
C.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
-
D.
national church council
A national church council is a governing or advisory body composed of representatives from across a country’s churches that coordinates doctrine, policy, and common initiatives at the national level.
-
E.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
- F. None of above.
Provenance (1 batch)
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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:38 p.m.