Triple

T8330030
Position Surface form Disambiguated ID Type / Status
Subject Papyrus 75 E195051 entity
Predicate instanceOf P0 FINISHED
Object early Christian manuscript 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 manuscript
Context triple: [Papyrus 75, instanceOf, early Christian manuscript]
  • 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. Glagolitic manuscript
    A Glagolitic manuscript is a handwritten document produced using the Glagolitic alphabet, one of the earliest Slavic scripts, typically preserving religious, liturgical, or legal texts from the medieval Slavic cultural sphere.
  • C. ancient manuscripts
    Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
  • D. 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.
  • 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_69ca82e87f2c8190bdb71ee29dfc642d completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 5:56 p.m.