Triple
T24014943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anuttarayoga Tantra |
E594645
|
entity |
| Predicate | includesPracticeSystems |
P74486
|
FINISHED |
| Object | Guhyasamāja Tantra |
—
|
NE NERFINISHED |
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: Guhyasamāja Tantra | Statement: [Anuttarayoga Tantra, includesPracticeSystems, Guhyasamāja Tantra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPracticeSystems Context triple: [Anuttarayoga Tantra, includesPracticeSystems, Guhyasamāja Tantra]
-
A.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
B.
coversPractice
chosen
Indicates that one entity includes, addresses, or provides instruction on a particular practice or set of practices.
-
C.
settingOfPractice
Indicates the context or environment in which a particular practice, activity, or procedure is carried out.
-
D.
isPracticedAt
Indicates that an activity, skill, or discipline is regularly performed or carried out at a particular location or context.
-
E.
hasPracticeForm
Indicates that an entity is associated with, or takes place in, a particular form or mode of practice.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a32374819094dcb42abf18c033 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.