Triple
T26807853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Orthodox Eparchy of Belgrade and Karlovci |
E671891
|
entity |
| Predicate | hasClergyRankOver |
P173690
|
FINISHED |
| Object | priests |
—
|
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: priests | Statement: [Serbian Orthodox Eparchy of Belgrade and Karlovci, hasClergyRankOver, priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClergyRankOver Context triple: [Serbian Orthodox Eparchy of Belgrade and Karlovci, hasClergyRankOver, priests]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
C.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
D.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
E.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
- F. None of above. chosen
Provenance (4 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 27, 2026, 4:27 a.m.