Triple
T33642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy See |
E670
|
entity |
| Predicate | hasConcordatWith |
P1108
|
FINISHED |
| Object | many sovereign states |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: many sovereign states | Statement: [Holy See, hasConcordatWith, many sovereign states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcordatWith Context triple: [Holy See, hasConcordatWith, many sovereign states]
-
A.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
B.
hasEcumenicalAgreementWith
chosen
Indicates that two religious organizations or denominations are formally bound by a mutual ecumenical agreement recognizing shared faith, cooperation, or unity.
-
C.
hasSupranationalInstitution
Indicates that an entity is associated with or governed by an institution that operates above the level of individual nation-states.
-
D.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
E.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
- F. None of above.
Provenance (3 batches)
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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.