Triple
T29693152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martyrdoms of the Saints (hagiographic texts) |
E751267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hagiographic text collection |
C10140
|
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: hagiographic text collection Context triple: [Martyrdoms of the Saints (hagiographic texts), instanceOf, hagiographic text collection]
-
A.
hagiographical collection
chosen
A hagiographical collection is an assemblage of texts or narratives that recount and celebrate the lives, virtues, and miracles of saints or holy figures, often for devotional or didactic purposes.
-
B.
patristic text collection
A patristic text collection is an organized compilation of writings by the early Christian Church Fathers, typically gathered for study, reference, or theological analysis.
-
C.
prophetic text collection
A prophetic text collection is an organized body of writings that record, preserve, and present messages believed to be divinely inspired or visionary, often concerning future events, moral guidance, or spiritual insight.
-
D.
hagiographical figure
A hagiographical figure is a person—often a saint or revered religious individual—whose life is portrayed in an idealized, morally exemplary manner within devotional or biographical narratives.
-
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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:18 p.m.