Triple
T35981006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longchen Rabjam |
E1040561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tibetan Buddhist meditation master |
C62501
|
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 meditation master Context triple: [Longchen Rabjam, instanceOf, Tibetan Buddhist meditation master]
-
A.
Tibetan Buddhist monk
A Tibetan Buddhist monk is a religious practitioner who has taken monastic vows within the Tibetan Buddhist tradition, dedicating their life to meditation, study, ritual practice, and the pursuit of enlightenment for the benefit of all beings.
-
B.
Dzogchen master
chosen
A Dzogchen master is a highly realized teacher in the Tibetan Buddhist tradition who directly guides students to recognize and stabilize the innate, primordial nature of mind beyond conceptual elaboration.
-
C.
Buddhist spiritual leader
A Buddhist spiritual leader is a respected teacher and guide who embodies Buddhist principles, offers instruction in doctrine and meditation, and supports the spiritual development of a community.
-
D.
Shingon Buddhist monk
A Shingon Buddhist monk is a practitioner of Japanese esoteric Buddhism who undergoes rigorous training in mantra, mudra, and mandala rituals to realize enlightenment and compassion for all beings.
-
E.
Chinese Buddhist monk
A Chinese Buddhist monk is a religious practitioner in China who has renounced lay life to follow the Buddhist monastic code, engaging in meditation, study, ritual, and community service within a Chinese cultural and historical context.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.