Triple
T26508942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadyojata |
E669625
|
entity |
| Predicate | associatedWithEnergy |
P188106
|
FINISHED |
| Object | creative shakti of 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: creative shakti of Shiva | Statement: [Sadyojata, associatedWithEnergy, creative shakti of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEnergy Context triple: [Sadyojata, associatedWithEnergy, creative shakti of Shiva]
-
A.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
B.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
C.
hasEnergyConcept
chosen
Indicates that one entity is associated with, characterized by, or defined in terms of a particular concept of energy.
-
D.
symbolForEnergy
Indicates that one entity serves as a symbolic representation or notation for the concept of energy associated with another entity.
-
E.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: April 27, 2026, 1:18 a.m.