Triple
T29841216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryazan Eparchy |
E757801
|
entity |
| Predicate | hasClericalRankHead |
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: [Ryazan Eparchy, hasClericalRankHead, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalRankHead Context triple: [Ryazan Eparchy, hasClericalRankHead, bishop]
-
A.
hasClergyRankOver
Indicates that one clergy member holds a higher ecclesiastical rank or authority than another within a religious hierarchy.
-
B.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
C.
hasClericTitle
Indicates that an entity holds or is designated by a specific clerical or religious title in relation to another entity or context.
-
D.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
E.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 5:39 p.m.