Triple

T17610424
Position Surface form Disambiguated ID Type / Status
Subject corpus of Gregory of Nyssa E428951 entity
Predicate instanceOf P0 FINISHED
Object theological writings collection C25962 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: theological writings collection
Context triple: [corpus of Gregory of Nyssa, instanceOf, theological writings collection]
  • A. theological work
    A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
  • B. Christian theological corpus chosen
    The Christian theological corpus is the body of writings, doctrines, and interpretive traditions that systematically articulate and reflect on Christian beliefs about God, Christ, salvation, the Church, and the ultimate destiny of creation.
  • C. theological document
    A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
  • D. theological journal
    A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
  • E. collection of ecclesiastical documents
    A collection of ecclesiastical documents is an organized set of official church writings—such as decrees, letters, liturgical texts, and doctrinal statements—preserved for reference, governance, and historical record within a religious community.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
Created at: April 10, 2026, 5:51 a.m.