Triple
T34021366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aṣṭāṅga Yoga |
E872389
|
entity |
| Predicate | hasMeditativeComponent |
P198795
|
FINISHED |
| Object | Dhāraṇā, Dhyāna, Samādhi |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Dhāraṇā, Dhyāna, Samādhi | Statement: [Aṣṭāṅga Yoga, hasMeditativeComponent, Dhāraṇā, Dhyāna, Samādhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeditativeComponent Context triple: [Aṣṭāṅga Yoga, hasMeditativeComponent, Dhāraṇā, Dhyāna, Samādhi]
-
A.
hasMeditativeSound
Indicates that something produces or is associated with a sound conducive to meditation or meditative practice.
-
B.
hasMeditativeGrooves
Indicates that something features grooves or patterns specifically designed to facilitate or enhance meditative or contemplative experiences.
-
C.
meditationType
Indicates the specific kind or category of meditation practice associated with an entity.
-
D.
hasSamadhi
Indicates that an entity possesses or has attained the state of samadhi (deep meditative absorption or spiritual concentration) in relation to another context or state.
-
E.
meditationSubject
Indicates that one entity is the topic, focus, or object upon which another entity meditates.
- F. None of above. chosen
Provenance (4 batches)
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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69ff069ddf948190bdfe438953249dd0 |
completed | May 9, 2026, 10:04 a.m. |
Created at: May 1, 2026, 1:51 a.m.