Triple
T11170529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Astorga |
E264260
|
entity |
| Predicate | hasClericalTerritoryType |
P8670
|
FINISHED |
| Object | diocesan territory |
—
|
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: diocesan territory | Statement: [Roman Catholic Diocese of Astorga, hasClericalTerritoryType, diocesan territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalTerritoryType Context triple: [Roman Catholic Diocese of Astorga, hasClericalTerritoryType, diocesan territory]
-
A.
hasClericalProvince
Indicates that one ecclesiastical jurisdiction or entity is part of, or belongs to, a specific clerical (church) province.
-
B.
ecclesiasticalTerritory
chosen
Indicates that one entity is an ecclesiastical (church-governed) jurisdiction or territory associated with another entity, such as a religious organization or authority.
-
C.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
D.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
E.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.