Triple
T21313281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradyumna |
E525398
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Kamadeva |
—
|
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: Kamadeva | Statement: [Pradyumna, associatedWith, Kamadeva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kamadeva Context triple: [Pradyumna, associatedWith, Kamadeva]
-
A.
Kamadeva
chosen
Kamadeva is the Hindu god of love and desire, often depicted as a youthful archer who inspires romantic attraction.
-
B.
Sadyojata
Sadyojata is one of the five faces of Lord Shiva, symbolizing creation and the westward aspect of the deity in Shaivite tradition.
-
C.
Vritra
Vritra is a powerful serpent or dragon-like demon in Hindu mythology, best known as the adversary slain by the god Indra to release the waters and restore cosmic order.
-
D.
Rudra
Rudra is a fierce and storm-associated Vedic deity later identified with the Hindu god Shiva, known for his destructive and healing powers.
-
E.
Pururavas
Pururavas is a legendary king in Hindu mythology, often regarded as an early lunar dynasty ruler and famed for his love story with the celestial nymph Urvashi.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcc6350819093763632b7e6e4ac |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 4:27 p.m.