Triple
T7153727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement between the Holy See and the Oriental Republic of Uruguay (2012) |
E166755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holy See concordat |
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: Holy See concordat Context triple: [Agreement between the Holy See and the Oriental Republic of Uruguay (2012), instanceOf, Holy See concordat]
-
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.
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.
-
C.
organ of the Holy See
An organ of the Holy See is an official body, institution, or office that acts on behalf of the Holy See to exercise its spiritual, administrative, diplomatic, or judicial functions within the Catholic Church and in relations with states and international organizations.
-
D.
ecumenical decree
An ecumenical decree is an authoritative formal decision or doctrinal statement issued by an ecumenical council of the Church, binding on the whole Christian community it governs.
-
E.
ecclesiastical law code
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
- 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.