Triple
T13097542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan Tengyur |
E310630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tibetan Buddhist text collection |
C32446
|
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: Tibetan Buddhist text collection Context triple: [Tibetan Tengyur, instanceOf, Tibetan Buddhist text collection]
-
A.
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.
-
B.
Buddhist historical compendium
A Buddhist historical compendium is a comprehensive work that systematically collects, organizes, and interprets events, figures, texts, and developments across the history of Buddhism.
-
C.
Pure Land Buddhist text
A Pure Land Buddhist text is a religious scripture that teaches devotion to Amitābha Buddha and describes the practices, vows, and paradisiacal realms associated with rebirth in the Pure Land.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
Created at: April 9, 2026, 9:04 p.m.