Triple
T4017049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Ordinariate of Peru |
E91187
|
entity |
| Predicate | establishedAsVicariate |
P53954
|
FINISHED |
| Object | 15 May 1943 |
—
|
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: 15 May 1943 | Statement: [Military Ordinariate of Peru, establishedAsVicariate, 15 May 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsVicariate Context triple: [Military Ordinariate of Peru, establishedAsVicariate, 15 May 1943]
-
A.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
B.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
C.
gainedIndependenceAsSeparateDiocese
Indicates that an ecclesiastical jurisdiction became an independent diocese, separate from the authority or structure of a previously associated diocese.
-
D.
servedInDiocese
Indicates that one entity held a role or performed official duties within the jurisdiction of a particular diocese.
-
E.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
- F. None of above. chosen
Provenance (4 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaea76c48190add2e7cee180e8b1 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:35 p.m.