Triple
T7315109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement between the Holy See and the Republic of Poland on military chaplaincy (1991) |
E168389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | concordat-type agreement |
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: concordat-type agreement Context triple: [Agreement between the Holy See and the Republic of Poland on military chaplaincy (1991), instanceOf, concordat-type agreement]
-
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.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
C.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
D.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
E.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
- 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.