Triple
T5345949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Nigeria |
E124054
|
entity |
| Predicate | hasDioceses |
P36042
|
FINISHED |
| Object | numerous dioceses across Nigeria |
—
|
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: numerous dioceses across Nigeria | Statement: [Church of Nigeria, hasDioceses, numerous dioceses across Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDioceses Context triple: [Church of Nigeria, hasDioceses, numerous dioceses across Nigeria]
-
A.
hasDiocesesOrDistricts
chosen
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.
numberOfDioceses
Indicates the total count of dioceses associated with a given entity.
-
D.
hasArchdiocese
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
-
E.
hasSuffraganDiocese
Indicates that one diocese is subordinate to and under the ecclesiastical jurisdiction of another 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ec46ac81908e45ffb1b7a71507 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.