Triple
T34747247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Creed of Antioch |
E1001670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 4th-century Christian text |
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 text Context triple: [Second Creed of Antioch, instanceOf, 4th-century Christian text]
-
A.
early medieval Christian text
An early medieval Christian text is a written work produced roughly between the 5th and 11th centuries that reflects and shapes Christian theology, liturgy, devotion, or ecclesiastical practice within the cultural and political contexts of early medieval Europe and the Mediterranean.
-
B.
Coptic Christian text
A Coptic Christian text is a religious or theological work written in the Coptic language, reflecting the beliefs, liturgy, scripture, and spiritual traditions of the Coptic Orthodox and related Christian communities of Egypt.
-
C.
5th-century text
A 5th-century text is a written work created or compiled between 401 and 500 CE, reflecting the linguistic, cultural, religious, and intellectual contexts of that historical period.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.