Triple
T17980901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundalini |
E449597
|
entity |
| Predicate | effectBelief |
P85237
|
FINISHED |
| Object | spiritual awakening |
—
|
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: spiritual awakening | Statement: [Kundalini, effectBelief, spiritual awakening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectBelief Context triple: [Kundalini, effectBelief, spiritual awakening]
-
A.
invokesBeliefIn
chosen
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
B.
laterBelief
Indicates that an agent holds a particular belief at a time that is later than some referenced earlier time or belief state.
-
C.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
-
D.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
E.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b20431588190a5fe2148a61de403 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.