Triple
T36598520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abgar correspondence |
E902861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian legend |
C13506
|
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 legend Context triple: [Abgar correspondence, instanceOf, early Christian legend]
-
A.
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.
-
B.
early Christian work
chosen
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.
-
C.
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.
-
D.
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.
-
E.
legendary Christian saint
A legendary Christian saint is a revered figure, often of uncertain historicity, whose life story blends pious tradition, miracle tales, and moral exemplarity to inspire faith and devotion within Christian communities.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.