Triple
T34080283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Baker |
E874018
|
entity |
| Predicate | renamedAsDioceseOfBaker |
P178407
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Diocese of Baker, renamedAsDioceseOfBaker, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedAsDioceseOfBaker Context triple: [Diocese of Baker, renamedAsDioceseOfBaker, 1952]
-
A.
establishedAsCurrentDiocese
Indicates that an ecclesiastical jurisdiction was formally constituted or recognized in its present status as a diocese.
-
B.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
C.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
D.
restoredAsDiocese
Indicates that an ecclesiastical jurisdiction was re-established or reinstated with the status and functions of a diocese after having been previously suppressed, merged, or otherwise ceased to exist as such.
-
E.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:52 a.m.