Triple
T430024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheranism |
E9691
|
entity |
| Predicate | liturgicalSeasonObserved |
P9168
|
FINISHED |
| Object | Advent |
—
|
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: Advent | Statement: [Lutheranism, liturgicalSeasonObserved, Advent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalSeasonObserved Context triple: [Lutheranism, liturgicalSeasonObserved, Advent]
-
A.
liturgicalSeasonVariation
Indicates that something changes or differs depending on the liturgical season within a religious calendar or worship cycle.
-
B.
usesLiturgicalCalendar
chosen
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
C.
hasLiturgicalCycle
Indicates that one entity follows, observes, or is structured according to a particular liturgical cycle associated with another entity.
-
D.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeedf68c81908473d6c6600961bd |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.