Triple
T2597319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran Church–Missouri Synod |
E58261
|
entity |
| Predicate | historicalLanguageOfWorship |
P18499
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Lutheran Church–Missouri Synod, historicalLanguageOfWorship, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageOfWorship Context triple: [Lutheran Church–Missouri Synod, historicalLanguageOfWorship, German]
-
A.
usesPrimaryLiturgicalLanguageHistorically
chosen
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
-
B.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
D.
historicalLanguageCenter
Indicates that a location has served as a significant hub or focal point for the development, use, or study of a particular language in the past.
-
E.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4548b1081909d28f88ea5e14202 |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.