Triple
T24842427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Pentecost |
E621650
|
entity |
| Predicate | troparionTheme |
P11561
|
FINISHED |
| Object | calling the thirsty to drink |
—
|
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: calling the thirsty to drink | Statement: [Mid-Pentecost, troparionTheme, calling the thirsty to drink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: troparionTheme Context triple: [Mid-Pentecost, troparionTheme, calling the thirsty to drink]
-
A.
hasTroparion
Indicates that one entity is associated with or possesses a specific troparion (a liturgical hymn or chant).
-
B.
liturgicalTheme
chosen
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
C.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
D.
verse49_10Theme
Indicates that the subject is thematically related to or exemplifies the central theme expressed in verse 49:10.
-
E.
prophecyTheme
Indicates that the relationship or action centers on the theme, content, or subject matter of a prophecy.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:19 a.m.