Triple
T30227805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashta Sakhi |
E768539
|
entity |
| Predicate | secondaryDevotionTo |
P21326
|
FINISHED |
| Object | Krishna |
—
|
NE NERFINISHED |
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: Krishna | Statement: [Ashta Sakhi, secondaryDevotionTo, Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryDevotionTo Context triple: [Ashta Sakhi, secondaryDevotionTo, Krishna]
-
A.
associatedDevotion
chosen
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryMissionField
Indicates a secondary or supporting operational area or objective associated with the primary mission.
-
D.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
E.
evidenceOfDevotion
Indicates that one entity serves as proof or demonstration of another entity’s devotion or commitment.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 29, 2026, 7:36 p.m.