Triple
T4838709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Rosary |
E108126
|
entity |
| Predicate | promulgatedInDocument |
P25579
|
FINISHED |
| Object | Consueverunt Romani Pontifices |
—
|
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: Consueverunt Romani Pontifices | Statement: [Holy Rosary, promulgatedInDocument, Consueverunt Romani Pontifices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promulgatedInDocument Context triple: [Holy Rosary, promulgatedInDocument, Consueverunt Romani Pontifices]
-
A.
institutedByDocument
chosen
Indicates that something (such as a rule, organization, or status) is formally established or created by a specific document.
-
B.
promulgatedAt
Indicates the time or date at which an official rule, law, or document is formally issued or put into effect.
-
C.
promulgates
Indicates the act of formally declaring, publishing, or putting a law, rule, or doctrine into official effect.
-
D.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
E.
adoptedDocument
Indicates that an authoritative body has formally approved and accepted a specific document as official or binding.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.