Triple
T6362466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catholic Church in Chile |
E143143
|
entity |
| Predicate | hasDioceseType |
P21505
|
FINISHED |
| Object | archdiocese |
—
|
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: archdiocese | Statement: [Catholic Church in Chile, hasDioceseType, archdiocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDioceseType Context triple: [Catholic Church in Chile, hasDioceseType, archdiocese]
-
A.
hasParishType
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
B.
hasCatholicDiocese
Indicates that a specified place or region falls under the jurisdiction of a particular Catholic diocese.
-
C.
hasArchdiocese
chosen
Indicates that an entity serves as the archdiocese (ecclesiastical jurisdiction) associated with another entity, such as a church, region, or religious organization.
-
D.
hasDioceseFunction
Indicates that an entity serves in a specific functional role or capacity within a diocese.
-
E.
hasDiocesesOrDistricts
Indicates that an organization or authority oversees one or more dioceses or districts within its jurisdiction.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680c02b481908618317566e31a5c |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.