Triple
T34150696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamika Ekadashi |
E875984
|
entity |
| Predicate | observanceGoal |
P129787
|
FINISHED |
| Object | pleasing Lord Vishnu |
—
|
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: pleasing Lord Vishnu | Statement: [Kamika Ekadashi, observanceGoal, pleasing Lord Vishnu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceGoal Context triple: [Kamika Ekadashi, observanceGoal, pleasing Lord Vishnu]
-
A.
devotionalPracticeGoal
chosen
Indicates the intended spiritual, moral, or personal outcome that a devotional practice is meant to achieve.
-
B.
experienceGoal
Indicates that an entity has a desired outcome or objective it aims to achieve through its experiences or actions.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
E.
oversightGoal
Indicates that an entity has the purpose or objective of overseeing, supervising, or monitoring another entity, process, or activity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:54 a.m.