Triple
T10327550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Košice |
E242797
|
entity |
| Predicate | elevatedToEparchy |
P88303
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Eparchy of Košice, elevatedToEparchy, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToEparchy Context triple: [Eparchy of Košice, elevatedToEparchy, 2008]
-
A.
elevatedToEparchyFrom
Indicates that a religious jurisdiction was raised in status to an eparchy from a specified prior ecclesiastical unit or rank.
-
B.
elevatedToArcheparchy
Indicates that a church jurisdiction or eparchy has been raised in rank or status to that of an archeparchy.
-
C.
elevatedToArchdioceseBy
Indicates that one ecclesiastical jurisdiction was raised in rank to an archdiocese by a particular authority or decision.
-
D.
establishedAsEparchy
chosen
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of an eparchy.
-
E.
hasEparchy
Indicates that one entity possesses, oversees, or is associated with a specific eparchy (a territorial jurisdiction of an Eastern Christian church).
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cf21e08190bf605daeea0d9dcf |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.