Triple
T22048576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narasimha Jayanti |
E544824
|
entity |
| Predicate | associatedFigure |
P1183
|
FINISHED |
| Object | Prahlada |
—
|
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: Prahlada | Statement: [Narasimha Jayanti, associatedFigure, Prahlada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prahlada Context triple: [Narasimha Jayanti, associatedFigure, Prahlada]
-
A.
Prahlada
chosen
Prahlada is a revered devotee of the Hindu god Vishnu, celebrated for his unwavering faith and righteousness in defiance of his tyrannical father.
-
B.
Pradyumna
Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
-
C.
Aniruddha
Aniruddha is a prominent figure in Hindu mythology, known as the grandson of Krishna and a heroic member of the Yadava dynasty.
-
D.
Parikshit
Parikshit is a king from the Mahabharata epic, known as the grandson of Arjuna and successor to the throne of Hastinapura.
-
E.
Govind
Govind is a Hindu deity, commonly identified with Lord Krishna or Vishnu, who is venerated as the divine protector and guide of devotees.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283191e48190b4ddc84138243327 |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:26 p.m.