Triple
T37517533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo I’s Tome |
E932675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 5th-century Christian text |
C14109
|
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: 5th-century Christian text Context triple: [Leo I’s Tome, instanceOf, 5th-century Christian text]
-
A.
4th-century Christian text
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.
5th-century text
chosen
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.
-
C.
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.
-
D.
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.
-
E.
early medieval religious text
An early medieval religious text is a written work produced roughly between the 5th and 11th centuries that conveys, interprets, or codifies spiritual beliefs, practices, or doctrines within a particular religious tradition.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.