Triple
T33060968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadvirna |
E845972
|
entity |
| Predicate | hasReligiousCommunityType |
P22135
|
FINISHED |
| Object | Ukrainian Greek Catholic Church |
E45017
|
NE 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: Ukrainian Greek Catholic Church | Statement: [Nadvirna, hasReligiousCommunityType, Ukrainian Greek Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousCommunityType Context triple: [Nadvirna, hasReligiousCommunityType, Ukrainian Greek Catholic Church]
-
A.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
B.
hasFormerReligiousCommunity
Indicates that an entity previously belonged to a particular religious community but is no longer a member of it.
-
C.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
D.
hasReligiousStructureType
Indicates that a religious structure is classified as being of a specific type or category of religious building.
-
E.
hasReligiousOrganization
chosen
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
- F. None of above.
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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0340784c488190aa6c7c9be2e8a434 |
completed | May 12, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e523d314819094a9e1912b42655e |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_6a033f33eddc819091507716f6ed7d7d |
completed | May 12, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:25 a.m.