Triple
T38697295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of the Episcopal Diocese of Mississippi |
E950036
|
entity |
| Predicate | hasDiocesanFunctions |
P67790
|
FINISHED |
| Object | ordinations |
—
|
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: ordinations | Statement: [Cathedral of the Episcopal Diocese of Mississippi, hasDiocesanFunctions, ordinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiocesanFunctions Context triple: [Cathedral of the Episcopal Diocese of Mississippi, hasDiocesanFunctions, ordinations]
-
A.
hasDioceseFunction
chosen
Indicates that an entity serves in a specific functional role or capacity within a diocese.
-
B.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
C.
hasDiocesanStatus
Indicates that an ecclesiastical jurisdiction or entity holds official recognition and authority as a diocese within a church hierarchy.
-
D.
hasDiocesanSee
Indicates that a bishop or ecclesiastical jurisdiction holds its official diocesan seat or central cathedral in a particular location.
-
E.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:33 p.m.