Triple
T24983639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shambhavopaya |
E625240
|
entity |
| Predicate | practiceStyle |
P12790
|
FINISHED |
| Object | inward, formless contemplation |
—
|
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: inward, formless contemplation | Statement: [Shambhavopaya, practiceStyle, inward, formless contemplation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practiceStyle Context triple: [Shambhavopaya, practiceStyle, inward, formless contemplation]
-
A.
practiceType
chosen
Indicates the specific kind or category of practice associated with an entity or activity.
-
B.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
C.
practiceFocus
Indicates that an entity directs its practice or training efforts specifically toward another entity or subject.
-
D.
settingOfPractice
Indicates the context or environment in which a particular practice, activity, or procedure is carried out.
-
E.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
- F. None of above.
Provenance (3 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f449082d10819083b7bc99fe99023e |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.