Triple
T38018046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qianlong Canon |
E948548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese Buddhist canon |
C29671
|
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: Chinese Buddhist canon Context triple: [Qianlong Canon, instanceOf, Chinese Buddhist canon]
-
A.
Chinese Buddhist literature
chosen
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.
-
B.
Chinese Buddhist classic
A Chinese Buddhist classic is a foundational religious text, translated or composed in Chinese, that transmits Buddhist doctrines, practices, and narratives within the Chinese cultural and historical context.
-
C.
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.
-
D.
Theravada canon text
A Theravada canon text is a scripture belonging to the Pāli Tipiṭaka, regarded in Theravada Buddhism as an authoritative record of the Buddha’s teachings and related monastic and doctrinal traditions.
-
E.
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.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.