Triple
T4767929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zechariah |
E105856
|
entity |
| Predicate | BenedictusTheme |
P11561
|
FINISHED |
| Object | praise for God’s salvation |
—
|
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: praise for God’s salvation | Statement: [Zechariah, BenedictusTheme, praise for God’s salvation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BenedictusTheme Context triple: [Zechariah, BenedictusTheme, praise for God’s salvation]
-
A.
liturgicalTheme
chosen
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
B.
synodTheme
Indicates the central topic or guiding subject around which a particular synod is organized.
-
C.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
D.
liturgicalMoment
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
-
E.
dominantRite
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.