Triple
T12055271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of St. Philip |
E287024
|
entity |
| Predicate | associatedBishopric |
P64718
|
FINISHED |
| Object | Bishop of Atlanta |
—
|
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: Bishop of Atlanta | Statement: [Cathedral of St. Philip, associatedBishopric, Bishop of Atlanta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBishopric Context triple: [Cathedral of St. Philip, associatedBishopric, Bishop of Atlanta]
-
A.
linkedDiocese
Indicates a formal association or connection established between one diocese and another.
-
B.
suffraganOf
Indicates that one ecclesiastical jurisdiction or bishop is subordinate to and under the authority of a particular metropolitan or archdiocesan see.
-
C.
isTitularChurchOf
Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
-
D.
belongsToArchdeaconry
Indicates that one ecclesiastical unit or entity is administratively part of, or under the jurisdiction of, a specific archdeaconry.
-
E.
dioceseBishop
chosen
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.