Triple
T12162834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avataṃsaka Sutra |
E289750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canonical text in East Asian Buddhism |
C16429
|
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: canonical text in East Asian Buddhism Context triple: [Avataṃsaka Sutra, instanceOf, canonical text in East Asian Buddhism]
-
A.
Chan Buddhist text
A Chan Buddhist text is a written work that records the teachings, dialogues, practices, and stories central to the Chan (Zen) tradition, emphasizing direct insight into one’s true nature beyond conceptual thought.
-
B.
Chan Buddhist literature
Chan Buddhist literature encompasses the sermons, dialogues, koans, treatises, and recorded sayings that articulate the teachings, practices, and distinctive rhetoric of the Chan (Zen) tradition in China and its later East Asian developments.
-
C.
Chinese Buddhist literature
Chinese Buddhist literature encompasses the vast body of scriptures, commentaries, translations, narratives, and ritual texts produced in the Chinese language that transmit, interpret, and adapt Buddhist teachings within Chinese cultural and historical contexts.
-
D.
Song dynasty Zen text
A Song dynasty Zen text is a written work produced during China’s Song dynasty (960–1279) that records, systematizes, or comments on Chan (Zen) Buddhist teachings, practices, and dialogues.
-
E.
Sutra literature
chosen
Sutra literature is a body of sacred texts, primarily in Hinduism, Buddhism, and Jainism, composed in concise aphoristic form to systematically present spiritual teachings, doctrines, and practices.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.