Triple
T26277847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy See–state relations |
E660623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aspect of Holy See diplomacy |
C41113
|
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: aspect of Holy See diplomacy Context triple: [Holy See–state relations, instanceOf, aspect of Holy See diplomacy]
-
A.
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.
-
B.
Catholic diplomat
A Catholic diplomat is an official representative who conducts negotiations and fosters relations on behalf of the Catholic Church or a Catholic-majority state, guided by both diplomatic protocol and Catholic moral and social teaching.
-
C.
Vatican expert
A Vatican expert is a specialist with deep knowledge of the Holy See’s history, governance, diplomacy, doctrine, and internal institutions, able to interpret and contextualize Vatican actions and policies.
-
D.
Vatican security official
A Vatican security official is a member of the Holy See’s protective services responsible for safeguarding the Pope, Vatican City, and its institutions through intelligence, surveillance, and physical security operations.
-
E.
ecclesiastical statesman
chosen
An ecclesiastical statesman is a religious leader who skillfully engages in political and diplomatic affairs to shape church and state relations.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 9:57 p.m.