Triple
T1451163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter Mirifica |
E31293
|
entity |
| Predicate | isConciliarDocumentNumber |
P3247
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Inter Mirifica, isConciliarDocumentNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConciliarDocumentNumber Context triple: [Inter Mirifica, isConciliarDocumentNumber, 2]
-
A.
documentNumber
chosen
Indicates the unique identifying number assigned to a specific document in the relationship.
-
B.
initialSignatoriesIncluded
Indicates that the specified entities were part of the original group that formally signed or endorsed an agreement or document.
-
C.
cameIntoForceRelatedDocument
Indicates that a document became legally effective or operational as a result of, or in connection with, another related document.
-
D.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
E.
ecclesiasticalDocumentOf
Indicates that one entity is an ecclesiastical (church-related) document that is issued by, belongs to, or is formally associated with another entity.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57bc0908190a57e6bc3d20d5e3c |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.