Triple
T17980907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundalini |
E449597
|
entity |
| Predicate | finalGoalBelief |
P129991
|
FINISHED |
| Object | union with Shiva |
—
|
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: union with Shiva | Statement: [Kundalini, finalGoalBelief, union with Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGoalBelief Context triple: [Kundalini, finalGoalBelief, union with Shiva]
-
A.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
B.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
C.
formerGoal
Indicates that an entity previously had a particular goal or objective, but no longer has it.
-
D.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.