Triple
T5075445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhima |
E114383
|
entity |
| Predicate | epithet |
P743
|
FINISHED |
| Object | Vayuputra |
E140341
|
NE 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: Vayuputra | Statement: [Bhima, epithet, Vayuputra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vayuputra Context triple: [Bhima, epithet, Vayuputra]
-
A.
Gangaputra
Gangaputra is an epithet of Bhishma, the revered warrior and elder statesman of the Indian epic Mahabharata, highlighting his divine lineage as the son of the river goddess Ganga.
-
B.
Pavanputra
chosen
Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
-
C.
Akrura
Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
-
D.
Kauravya
Kauravya is a Naga king from the Mahabharata, known as the father of the Naga princess Ulupi.
-
E.
Dasaratha
Dasaratha is the legendary king of Ayodhya in the Hindu epic Ramayana and the father of Lord Rama.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beba6be1248190bad40b869c8d0820 |
completed | March 21, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:39 p.m.