Triple
T16950308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly Hundred |
E411163
|
entity |
| Predicate | religiousCommemoration |
P31000
|
FINISHED |
| Object | prayers and liturgies in Ukrainian churches |
—
|
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: prayers and liturgies in Ukrainian churches | Statement: [Heavenly Hundred, religiousCommemoration, prayers and liturgies in Ukrainian churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCommemoration Context triple: [Heavenly Hundred, religiousCommemoration, prayers and liturgies in Ukrainian churches]
-
A.
commemoratesDoctrine
Indicates that one entity serves to honor, remember, or recognize a particular doctrine or set of teachings.
-
B.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
C.
religiousEvent
chosen
Indicates that an event is related to religious practices, observances, or ceremonies.
-
D.
commemoratesActivity
Indicates that one entity serves to honor, remember, or mark the occurrence of a particular activity or event.
-
E.
commemorationDescription
Indicates a descriptive statement that explains how an event, person, or thing is honored or remembered.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb6e5fc8190b1bd3ad1c2773685 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.