Triple
T24983619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shambhavopaya |
E625240
|
entity |
| Predicate | metaphysicalOrientation |
P4933
|
FINISHED |
| Object | non-dualism |
—
|
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: non-dualism | Statement: [Shambhavopaya, metaphysicalOrientation, non-dualism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metaphysicalOrientation Context triple: [Shambhavopaya, metaphysicalOrientation, non-dualism]
-
A.
positionOnMetaphysics
chosen
Indicates a relationship where an entity’s stance, view, or theoretical commitment regarding metaphysical questions or issues is specified.
-
B.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
C.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
D.
orientationOfDeity
Indicates the directional or positional alignment associated with a deity in relation to a reference point or context.
-
E.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or 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_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.