Triple
T10790661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelical Lutheran Church in Thuringia |
E254568
|
entity |
| Predicate | hasMainRite |
P13039
|
FINISHED |
| Object | Lutheran liturgy |
—
|
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: Lutheran liturgy | Statement: [Evangelical Lutheran Church in Thuringia, hasMainRite, Lutheran liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRite Context triple: [Evangelical Lutheran Church in Thuringia, hasMainRite, Lutheran liturgy]
-
A.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
B.
dominantRite
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
-
C.
containsRite
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
D.
hasPrimaryLiturgicalForm
chosen
Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious practice.
-
E.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f5b8248190a633dc44ae620a3a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.