Triple
T35854912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homoian creed |
E1036470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th-century Christian creed |
C61979
|
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: 4th-century Christian creed Context triple: [Homoian creed, instanceOf, 4th-century Christian creed]
-
A.
4th-century Christian text
chosen
A 4th-century Christian text is a written work produced within the Christian tradition during the 300s CE, reflecting the theological debates, doctrinal developments, and ecclesiastical practices of the early Church in that period.
-
B.
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.
-
C.
early Christian work
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
D.
era of Christian history
An era of Christian history is a distinct period characterized by particular theological developments, ecclesiastical structures, cultural influences, and historical events that shape the life and thought of the Christian church.
-
E.
group of early Christian writers
A group of early Christian writers are influential theologians and authors from the first centuries of Christianity whose works helped shape Christian doctrine, practice, and interpretation of Scripture.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.