Triple
T18884232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prahlada |
E461915
|
entity |
| Predicate | roleInNarasimhaStory |
P9987
|
FINISHED |
| Object | cause for Vishnu’s Narasimha incarnation |
—
|
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: cause for Vishnu’s Narasimha incarnation | Statement: [Prahlada, roleInNarasimhaStory, cause for Vishnu’s Narasimha incarnation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNarasimhaStory Context triple: [Prahlada, roleInNarasimhaStory, cause for Vishnu’s Narasimha incarnation]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
C.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
D.
roleInShivajisLife
Indicates the specific role, influence, or significance an entity had in the life of Shivaji.
-
E.
inRamayana
Indicates that the subject participates in, appears within, or is otherwise part of the events or narrative of the Ramayana.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d3dcec8190a468162c6a4482f6 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.