Triple
T25860595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regnans in Excelsis |
E651466
|
entity |
| Predicate | issuedByInstitution |
P155018
|
FINISHED |
| Object | Roman Curia |
—
|
NE NERFINISHED |
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: Roman Curia | Statement: [Regnans in Excelsis, issuedByInstitution, Roman Curia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedByInstitution Context triple: [Regnans in Excelsis, issuedByInstitution, Roman Curia]
-
A.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
B.
issuerOrganization
chosen
Indicates the organization that formally issues, grants, or authorizes a document, credential, or item.
-
C.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
D.
issuerOffice
Indicates the office or organizational unit that formally issues or authorizes something (such as a document, credential, or statement).
-
E.
grantedByInstitution
Indicates that something (such as a status, permission, or resource) is conferred or authorized by an institution.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 8:05 a.m.