Triple
T13545274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Lutheran churches |
E323492
|
entity |
| Predicate | retainsTraditionFrom |
P20591
|
FINISHED |
| Object | Western catholic 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: Western catholic liturgy | Statement: [European Lutheran churches, retainsTraditionFrom, Western catholic liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainsTraditionFrom Context triple: [European Lutheran churches, retainsTraditionFrom, Western catholic liturgy]
-
A.
retainsHeritageOf
Indicates that one entity preserves, maintains, or keeps alive the cultural, historical, or traditional legacy originating from another entity.
-
B.
traditionInheritedFrom
chosen
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
C.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
D.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
E.
mainTradition
Indicates that one entity represents the primary or dominant tradition 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.