Triple
T10992748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personal Ordinariates |
E259788
|
entity |
| Predicate | canErectParishes |
P96528
|
FINISHED |
| Object | within host dioceses |
—
|
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: within host dioceses | Statement: [Personal Ordinariates, canErectParishes, within host dioceses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canErectParishes Context triple: [Personal Ordinariates, canErectParishes, within host dioceses]
-
A.
parishesIncluded
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
B.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
C.
hasDiocesesOrDistricts
Indicates that an organization or authority oversees one or more dioceses or districts within its jurisdiction.
-
D.
hasDioceseEquivalent
Indicates that an entity possesses a jurisdictional unit that is functionally equivalent to a diocese, even if it has a different formal designation.
-
E.
hasArchdiocese
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
- F. None of above. chosen
Provenance (4 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d32f9081909def643571499521 |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.