Triple
T23766447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decretum Gelasianum |
E587392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian document |
C17548
|
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: early Christian document Context triple: [Decretum Gelasianum, instanceOf, early Christian document]
-
A.
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.
-
B.
early medieval Christian text
chosen
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.
-
C.
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.
-
D.
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.
-
E.
early Christian figure
An early Christian figure is an individual from the first centuries of Christianity who contributed to the formation, spread, or interpretation of the Christian faith through leadership, teaching, writing, or martyrdom.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:15 p.m.