Triple
T18884217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prahlada |
E461915
|
entity |
| Predicate | kingOf |
P44742
|
FINISHED |
| Object | Daityas |
—
|
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: Daityas | Statement: [Prahlada, kingOf, Daityas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daityas Context triple: [Prahlada, kingOf, Daityas]
-
A.
Daityas
chosen
Daityas are a race of powerful and often antagonistic beings in Hindu mythology, typically portrayed as formidable opponents of the gods.
-
B.
Rakshasas
Rakshasas are powerful, shape-shifting demon beings from Hindu mythology, often portrayed as malevolent antagonists in epics like the Ramayana.
-
C.
Kumbhandas
Kumbhandas was a prominent 16th-century devotional poet-saint of the Pushtimarg tradition, known for his heartfelt compositions dedicated to Lord Krishna.
-
D.
Devas
The Devas are celestial gods in Hindu mythology who play pivotal roles in the cosmic order and divine interventions depicted throughout the Ramayana.
-
E.
Andhaka
Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d3dcec8190a468162c6a4482f6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 10, 2026, 11:57 a.m.