Triple
T9124049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Evangelical Church in Germany |
E218928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church constitution |
C10543
|
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: church constitution Context triple: [Constitution of the Evangelical Church in Germany, instanceOf, church constitution]
-
A.
church document
chosen
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
-
B.
doctrinal constitution
A doctrinal constitution is a formal, foundational document that systematically defines, organizes, and governs the core beliefs, teachings, and authoritative principles of a religious or ideological tradition.
-
C.
liturgical constitution
A liturgical constitution is an authoritative ecclesiastical document that defines, regulates, and reforms the public worship and sacramental practices of a religious community.
-
D.
pastoral constitution
A pastoral constitution is an official teaching document of the Catholic Church, issued by an ecumenical council, that addresses doctrinal principles in relation to the practical, pastoral needs and life of the contemporary world.
-
E.
constitutional convention document
A constitutional convention document is the formal written record produced by a constitutional convention that outlines proposed or adopted foundational principles, governmental structures, and legal frameworks for a political entity.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:17 p.m.