Triple
T37736981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamp records (denglu) |
E940302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Buddhist biographical collection |
C29670
|
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: Buddhist biographical collection Context triple: [Lamp records (denglu), instanceOf, Buddhist biographical collection]
-
A.
Buddhist historical compendium
chosen
A Buddhist historical compendium is a comprehensive work that systematically collects, organizes, and interprets events, figures, texts, and developments across the history of Buddhism.
-
B.
Buddhist hymn collection
A Buddhist hymn collection is an organized compilation of devotional chants, verses, and songs used in Buddhist practice for worship, reflection, and the cultivation of spiritual insight.
-
C.
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.
-
D.
Buddhist library
A Buddhist library is a curated collection of texts, scriptures, commentaries, and related materials that support the study, practice, and preservation of Buddhist teachings and traditions.
-
E.
Buddhist miscellany
Buddhist miscellany is a conceptual class encompassing diverse, often peripheral or supplementary materials related to Buddhism, such as minor texts, commentaries, rituals, anecdotes, and cultural practices that do not fit neatly into core doctrinal or canonical categories.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.