Triple
T22895500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Châlons |
E568161
|
entity |
| Predicate | hasClericalRankOfOrdinary |
P5046
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [Diocese of Châlons, hasClericalRankOfOrdinary, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalRankOfOrdinary Context triple: [Diocese of Châlons, hasClericalRankOfOrdinary, bishop]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
C.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
D.
requiresOrdinationRank
Indicates that performing or holding a particular role, function, or responsibility is contingent upon having a specified level of ordination rank.
-
E.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801212808190b6471764d6c0b264 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.