Triple
T18884202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prahlada |
E461915
|
entity |
| Predicate | grandfather |
P979
|
FINISHED |
| Object | Kashyapa |
—
|
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: Kashyapa | Statement: [Prahlada, grandfather, Kashyapa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kashyapa Context triple: [Prahlada, grandfather, Kashyapa]
-
A.
Kashyapa
chosen
Kashyapa is a revered Vedic sage and progenitor in Hindu mythology, regarded as one of the ancient rishis and a patriarch of many gods, demons, and beings.
-
B.
Puspadanta
Puspadanta was a prominent Jain monk and poet known for composing important Apabhramsha-language works such as the Mahapurana.
-
C.
Shurasena
Shurasena was an ancient Yadava king of the Vrishni clan, known in Hindu tradition as the grandfather of Krishna and a prominent ruler in the Mahabharata era.
-
D.
Satyakāma Jābāla
Satyakāma Jābāla is a revered Vedic sage known for his exemplary truthfulness and devotion to spiritual knowledge, prominently featured in the Upanishadic tradition.
-
E.
Adishvara
Adishvara is an epithet of Rishabhanatha, revered in Jainism as the first Tirthankara and primordial spiritual teacher of the current time cycle.
- 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.