Triple
T7153634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concordat between the Holy See and Italy (1984 revision) |
E166753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty between state and church |
C3551
|
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: treaty between state and church Context triple: [Concordat between the Holy See and Italy (1984 revision), instanceOf, treaty between state and church]
-
A.
agreement between state and church
chosen
An agreement between state and church is a formal arrangement that defines the rights, responsibilities, and mutual relations between governmental authorities and religious institutions.
-
B.
state church
A state church is a religious organization officially endorsed and supported by a government, often enjoying special legal status and influence in public affairs.
-
C.
ecclesiastical state
An ecclesiastical state is a political entity in which the government is directly controlled by religious authorities, often with a church leader serving as the head of state.
-
D.
secular state
A secular state is a political entity in which government institutions and laws are officially neutral toward all religions, neither endorsing nor opposing any particular faith, and maintaining a clear separation between religious organizations and state authority.
-
E.
symbol of church–state conflict
A symbol of church–state conflict represents the tensions, struggles, and power negotiations between religious institutions and governmental authorities over influence, authority, and societal control.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.