Triple
T5451070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran orthodoxy |
E122370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period in church history |
C138
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: period in church history Context triple: [Lutheran orthodoxy, instanceOf, period in church history]
-
A.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
B.
early Christian church
The early Christian church was the loosely organized community of Jesus’ followers in the first few centuries CE, developing its beliefs, practices, and leadership structures as it spread throughout the Roman Empire and beyond.
-
C.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
D.
period in the Christian liturgical year
A period in the Christian liturgical year is a distinct, recurring span of time marked by specific theological themes, rituals, and observances that structure the worship and spiritual life of the Church.
-
E.
Christian liturgical season
A Christian liturgical season is a distinct, recurring period in the church year marked by specific theological themes, scriptures, prayers, and worship practices that shape the spiritual life and observances of the Christian community.
- F. None of above.
Provenance (1 batch)
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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:07 p.m.