Triple
T7314771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Agreement between the Holy See and the Palestine Liberation Organization |
E168380
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holy See treaty |
C566
|
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 treaty Context triple: [Basic Agreement between the Holy See and the Palestine Liberation Organization, instanceOf, Holy See treaty]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
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.
-
C.
Apostolic See
The Apostolic See is the episcopal jurisdiction of the Pope as the successor of Saint Peter, encompassing his supreme authority over the Catholic Church and its central governance.
-
D.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
E.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
Created at: March 27, 2026, 3:02 p.m.