Triple
T1464628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Diocese of Long Island |
E31591
|
entity |
| Predicate | dateErectedAsDiocese |
P16622
|
FINISHED |
| Object | 1868 |
—
|
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: 1868 | Statement: [Episcopal Diocese of Long Island, dateErectedAsDiocese, 1868]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateErectedAsDiocese Context triple: [Episcopal Diocese of Long Island, dateErectedAsDiocese, 1868]
-
A.
establishedAsDiocese
chosen
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
B.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
C.
hasCathedralStatusSince
Indicates the point in time from which something has held the official status of a cathedral.
-
D.
dioceseGovernedEnd
Indicates the point in time or event at which a diocese ceases to be under the governance or authority of a particular governing entity.
-
E.
hasArchdiocese
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ba2d5c81909ee85713de961fcb |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.