Triple
T2933102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Utah |
E79199
|
entity |
| Predicate | establishedAsMissionaryDistrict |
P41619
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [Diocese of Utah, establishedAsMissionaryDistrict, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsMissionaryDistrict Context triple: [Diocese of Utah, establishedAsMissionaryDistrict, 1867]
-
A.
foundedAsMissionaryDistrict
chosen
Indicates that an organization, typically a religious or ecclesiastical jurisdiction, was originally established in the form of a missionary district.
-
B.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
C.
establishedAsCongregationBy
Indicates that an entity was formally created or organized as a congregation by another specified agent or authority.
-
D.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
E.
missionaryRegion
Indicates that an entity carries out or is associated with missionary activities within a specified geographic region.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983a4ae08190aa1aeb2747abd1a1 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.