Triple
T10968997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Greek Catholic Church |
E259181
|
entity |
| Predicate | hasDiocesesCalled |
P94115
|
FINISHED |
| Object | eparchies |
—
|
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: eparchies | Statement: [Ukrainian Greek Catholic Church, hasDiocesesCalled, eparchies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiocesesCalled Context triple: [Ukrainian Greek Catholic Church, hasDiocesesCalled, eparchies]
-
A.
hasDiocesesOrDistricts
Indicates that an organization or authority oversees one or more dioceses or districts within its jurisdiction.
-
B.
hasCatholicDiocese
Indicates that a specified place or region falls under the jurisdiction of a particular Catholic diocese.
-
C.
hasDioceseEquivalent
chosen
Indicates that an entity possesses a jurisdictional unit that is functionally equivalent to a diocese, even if it has a different formal designation.
-
D.
hasDioceseFunction
Indicates that an entity serves in a specific functional role or capacity within a diocese.
-
E.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719800388190943a0bffa48a2731 |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.