Triple
T31416632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of Ungvár |
E801408
|
entity |
| Predicate | churchDiscipline |
P171846
|
FINISHED |
| Object | retained Byzantine rite |
—
|
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: retained Byzantine rite | Statement: [Union of Ungvár, churchDiscipline, retained Byzantine rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchDiscipline Context triple: [Union of Ungvár, churchDiscipline, retained Byzantine rite]
-
A.
viewOnChurchDiscipline
Indicates the stance or perspective an entity holds regarding the principles, practices, or application of church discipline.
-
B.
missionDiscipline
Indicates that an entity maintains adherence to rules, focus, and self-control in carrying out a mission or assigned task.
-
C.
sacramentalDiscipline
Indicates the rules, practices, and regulations governing how religious sacraments are properly administered and received.
-
D.
churchPolity
Indicates the form, structure, and governing system by which a church or religious community is organized and administered.
-
E.
withinChurch
Indicates that one entity is located inside or contained within a church.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:44 p.m.