Triple
T24983566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anavopaya section |
E625239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of scripture |
C17235
|
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: component of scripture Context triple: [Anavopaya section, instanceOf, component of scripture]
-
A.
section of a religious text
chosen
A section of a religious text is a distinct, thematically or structurally defined subdivision—such as a chapter, verse group, or discourse unit—within a sacred scripture that conveys a coherent portion of its teachings or narrative.
-
B.
figure in Latter-day Saint scripture
A figure in Latter-day Saint scripture is an individual, divine being, or symbolic personage who appears in or is referenced by the standard works of The Church of Jesus Christ of Latter-day Saints (the Bible, Book of Mormon, Doctrine and Covenants, and Pearl of Great Price), contributing to its narrative, doctrine, or theology.
-
C.
religious scripture
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.
-
D.
biblical text
A biblical text is a written work that forms part of the Bible, conveying religious narratives, laws, teachings, and poetry considered sacred and authoritative within Jewish and Christian traditions.
-
E.
commentary on scripture
A commentary on scripture is a detailed explanatory work that interprets, clarifies, and contextualizes sacred texts to aid understanding and application.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:02 a.m.