Triple
T10170393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novatian |
E235314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 3rd-century Christian |
C18623
|
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: 3rd-century Christian Context triple: [Novatian, instanceOf, 3rd-century Christian]
-
A.
2nd-century Christian
A 2nd-century Christian is a follower of Jesus within the diverse and developing early Church of the 100s CE, navigating emerging doctrines, sporadic persecution, and the transition from apostolic tradition to organized theology and community life.
-
B.
Late Antique Christian
A Late Antique Christian is an adherent of Christianity living between roughly the 3rd and 8th centuries CE, shaped by the Roman Empire’s transformation, emerging Christian institutions, and evolving theological and cultural debates.
-
C.
3rd-century Christian bishop
chosen
A 3rd-century Christian bishop was a regional church leader responsible for overseeing Christian communities, doctrine, and worship during a period of persecution and theological development in the Roman Empire.
-
D.
3rd-century event
A 3rd-century event is any significant historical occurrence that took place between the years 201 and 300 CE, encompassing political, social, cultural, military, or religious developments of that period.
-
E.
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.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:10 p.m.