Triple
T37295705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Catholic Eparchy of Saskatoon |
E925795
|
entity |
| Predicate | riteServed |
P187712
|
FINISHED |
| Object | Byzantine Rite faithful |
—
|
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: Byzantine Rite faithful | Statement: [Ukrainian Catholic Eparchy of Saskatoon, riteServed, Byzantine Rite faithful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riteServed Context triple: [Ukrainian Catholic Eparchy of Saskatoon, riteServed, Byzantine Rite faithful]
-
A.
riteStatus
Indicates the ceremonial or ritual state or condition that an entity currently holds within a specified rite or religious practice.
-
B.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
C.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
D.
writtenOut
Indicates that the content of one entity has been fully expressed, transcribed, or rendered in explicit written form as another entity.
-
E.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:16 p.m.