Triple
T34210131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhuvaneswari |
E877629
|
entity |
| Predicate | primaryDevoteeGoal |
P129787
|
FINISHED |
| Object | worldly prosperity |
—
|
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: worldly prosperity | Statement: [Bhuvaneswari, primaryDevoteeGoal, worldly prosperity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDevoteeGoal Context triple: [Bhuvaneswari, primaryDevoteeGoal, worldly prosperity]
-
A.
devotionalPracticeGoal
chosen
Indicates the intended spiritual, moral, or personal outcome that a devotional practice is meant to achieve.
-
B.
targetedDeity
Indicates that an action, event, or entity is specifically directed toward or aimed at a particular deity.
-
C.
pursuesDeity
Indicates that one entity actively seeks, follows, or strives to attain or engage with a deity.
-
D.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
E.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.