Triple
T26006491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Света Неделя |
E646773
|
entity |
| Predicate | епархия |
P2740
|
FINISHED |
| Object | Софийска епархия |
—
|
NE NERFINISHED |
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: Софийска епархия | Statement: [Света Неделя, епархия, Софийска епархия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: епархия Context triple: [Света Неделя, епархия, Софийска епархия]
-
A.
diocese
chosen
Indicates that one entity serves as the ecclesiastical district or jurisdiction under the authority of a bishop to which the other entity is related or belongs.
-
B.
hasEparchy
Indicates that one entity possesses, oversees, or is associated with a specific eparchy (a territorial jurisdiction of an Eastern Christian church).
-
C.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
D.
ecclesiasticalTerritory
Indicates that one entity is an ecclesiastical (church-governed) jurisdiction or territory associated with another entity, such as a religious organization or authority.
-
E.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.