Triple
T26851051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Sucre |
E676057
|
entity |
| Predicate | hasEcclesiasticalProvinceRank |
P92222
|
FINISHED |
| Object | metropolitan |
—
|
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: metropolitan | Statement: [Archdiocese of Sucre, hasEcclesiasticalProvinceRank, metropolitan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcclesiasticalProvinceRank Context triple: [Archdiocese of Sucre, hasEcclesiasticalProvinceRank, metropolitan]
-
A.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
B.
hasEcclesiasticalProvinceStatus
chosen
Indicates that an entity holds the official status or rank of an ecclesiastical province within a church’s organizational hierarchy.
-
C.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
D.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
E.
hasClericalProvince
Indicates that one ecclesiastical jurisdiction or entity is part of, or belongs to, a specific clerical (church) province.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:16 a.m.