Triple
T1402723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triodion |
E31620
|
entity |
| Predicate | hasLiturgicalTheme |
P11561
|
FINISHED |
| Object | repentance |
—
|
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: repentance | Statement: [Triodion, hasLiturgicalTheme, repentance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalTheme Context triple: [Triodion, hasLiturgicalTheme, repentance]
-
A.
liturgicalTheme
chosen
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
B.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
-
C.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
D.
hasSecondaryLiturgy
Indicates that an entity is associated with an additional, subordinate liturgical service or rite beyond its primary liturgy.
-
E.
hasLiturgicalCycle
Indicates that one entity follows, observes, or is structured according to a particular liturgical cycle associated with another entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39ef554819096c17bca5891829b |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.