Triple
T32367575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan of Varna and Veliki Preslav |
E827035
|
entity |
| Predicate | dioceseName |
P2740
|
FINISHED |
| Object | Varna and Veliki Preslav |
—
|
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: Varna and Veliki Preslav | Statement: [Metropolitan of Varna and Veliki Preslav, dioceseName, Varna and Veliki Preslav]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseName Context triple: [Metropolitan of Varna and Veliki Preslav, dioceseName, Varna and Veliki Preslav]
-
A.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
-
B.
administrativeDiocese
Indicates that one entity serves as the ecclesiastical administrative diocese responsible for the governance or oversight of another entity.
-
C.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
D.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
E.
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.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9f57048190819d133d4caba58e |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.