Triple
T10897118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eparchy of Nyíregyháza |
E257337
|
entity |
| Predicate | isEasternCatholic |
P96292
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eparchy of Nyíregyháza, isEasternCatholic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEasternCatholic Context triple: [Eparchy of Nyíregyháza, isEasternCatholic, true]
-
A.
isEasternCatholicPatriarch
Indicates that the subject holds the position of patriarch within an Eastern Catholic Church.
-
B.
isEcclesiasticalFormOf
Indicates that one term is the ecclesiastical (church-related or liturgical) form or variant of another term.
-
C.
isMetropolitanChurch
Indicates that a church holds metropolitan status, serving as the principal ecclesiastical authority over other churches within a defined region or province.
-
D.
hasDioceseEquivalent
Indicates that an entity possesses a jurisdictional unit that is functionally equivalent to a diocese, even if it has a different formal designation.
-
E.
hasCatholicosate
Indicates that an entity holds, contains, or is associated with a Catholicosate (the ecclesiastical jurisdiction or office of a Catholicos).
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d02e4c88190b8286078e90bf913 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.