Triple
T31253283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity Cathedral, Easton |
E796888
|
entity |
| Predicate | dioceseCathedralOf |
P35939
|
FINISHED |
| Object | Episcopal Diocese of Easton |
—
|
NE NERFINISHED |
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: Episcopal Diocese of Easton | Statement: [Trinity Cathedral, Easton, dioceseCathedralOf, Episcopal Diocese of Easton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseCathedralOf Context triple: [Trinity Cathedral, Easton, dioceseCathedralOf, Episcopal Diocese of Easton]
-
A.
cathedralProvince
Indicates the ecclesiastical province to which a cathedral (or its diocese) belongs within a church hierarchy.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
hasCathedralDiocese
chosen
Indicates that a cathedral is associated with or belongs to a particular diocese within a church’s administrative structure.
-
D.
cathedralName
Indicates that an entity has the specified name of a cathedral.
-
E.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:12 p.m.