Triple
T15724824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian biblical canon |
E381191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection of sacred texts |
C609
|
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: collection of sacred texts Context triple: [Christian biblical canon, instanceOf, collection of sacred texts]
-
A.
holy book
A holy book is a written text or collection of writings regarded by a religious community as divinely inspired or authoritative in matters of faith, morality, and spiritual practice.
-
B.
Tibetan Buddhist text collection
A Tibetan Buddhist text collection is an organized compilation of canonical and commentarial writings—such as sutras, tantras, philosophical treatises, and ritual manuals—preserved in Tibetan language and script for study, practice, and transmission of the Buddhist tradition.
-
C.
religious text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
D.
religious scripture
chosen
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
-
E.
religious literature
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.