Triple
T34085592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravana Nakshatra |
E874167
|
entity |
| Predicate | primaryShakti |
P205313
|
FINISHED |
| Object | power to connect and hear |
—
|
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: power to connect and hear | Statement: [Shravana Nakshatra, primaryShakti, power to connect and hear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryShakti Context triple: [Shravana Nakshatra, primaryShakti, power to connect and hear]
-
A.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
B.
primarySpirit
Indicates that one entity is the main or most fundamental spiritual essence associated with another entity.
-
C.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
D.
viewsShaktiAs
Indicates perceiving or regarding someone or something specifically as Shakti, or as an embodiment or manifestation of Shakti.
-
E.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:52 a.m.