Triple
T7120358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Calcutta |
E165932
|
entity |
| Predicate | establishedAsAnglicanDiocese |
P16622
|
FINISHED |
| Object | 1814 |
—
|
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: 1814 | Statement: [Diocese of Calcutta, establishedAsAnglicanDiocese, 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsAnglicanDiocese Context triple: [Diocese of Calcutta, establishedAsAnglicanDiocese, 1814]
-
A.
establishedAsDiocese
chosen
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
B.
establishedAsArchdioceseOn
Indicates that a religious jurisdiction was formally elevated to the status of an archdiocese on a specific date.
-
C.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
D.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
E.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61ca6a88190a0eb9f287e3b723c |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.