Triple
T17938506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhurya-rasa |
E448528
|
entity |
| Predicate | devoteeRole |
P58565
|
FINISHED |
| Object | lover of Krishna |
—
|
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: lover of Krishna | Statement: [Madhurya-rasa, devoteeRole, lover of Krishna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devoteeRole Context triple: [Madhurya-rasa, devoteeRole, lover of Krishna]
-
A.
roleInKrishnaLife
chosen
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
B.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
C.
devoteesSeek
Indicates that devoted followers actively seek out, pursue, or strive to approach the object of their devotion.
-
D.
roleAtTemple
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
E.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9455fc81908bf595f9ed42c624 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.