Triple
T13430000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyingma school |
E313581
|
entity |
| Predicate | hasScripturalCorpus |
P11799
|
FINISHED |
| Object | tantric texts |
—
|
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: tantric texts | Statement: [Nyingma school, hasScripturalCorpus, tantric texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScripturalCorpus Context triple: [Nyingma school, hasScripturalCorpus, tantric texts]
-
A.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
B.
scripturalCorpus
chosen
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
-
C.
scripturalCorpusAnalyzed
Indicates that a particular scriptural corpus has been examined or studied, typically in a systematic or scholarly manner.
-
D.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or tradition.
-
E.
consideredScriptureBy
Indicates that one party regards or recognizes a text or writing as sacred scripture.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed304ac8190a8021f749de8164c |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.