Triple
T3756888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesiastical History |
E82069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian historical work |
C11543
|
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: Christian historical work Context triple: [Ecclesiastical History, instanceOf, Christian historical work]
-
A.
Christian apologetic work
A Christian apologetic work is a text or presentation that systematically defends and explains the truth claims of Christianity using theological, philosophical, historical, and sometimes scientific arguments.
-
B.
Christian book
chosen
A Christian book is a written work that explores, explains, or is inspired by Christian beliefs, teachings, history, or spiritual practice, often aiming to encourage faith, understanding, or personal growth in its readers.
-
C.
Jewish historical work
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
-
D.
Christian devotional book
A Christian devotional book is a spiritual resource that offers daily or periodic reflections, prayers, and scripture-based insights to encourage personal growth and deepen one’s relationship with God.
-
E.
Christian instructional manual
A Christian instructional manual is a structured guide that explains Christian beliefs, practices, and moral teachings, providing step-by-step direction for living according to biblical principles.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.