Triple
T20305977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjaneya |
E505609
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Pavanputra |
—
|
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: Pavanputra | Statement: [Anjaneya, hasName, Pavanputra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pavanputra Context triple: [Anjaneya, hasName, Pavanputra]
-
A.
Pavanputra
chosen
Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
-
B.
Suryaputra
Suryaputra is an epithet of the legendary warrior Karna from the Indian epic Mahabharata, highlighting his divine parentage as the son of the sun god Surya.
-
C.
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.
-
D.
Santivarma
Santivarma was a ruler of the ancient Kadamba dynasty, an early Kannada-speaking royal house that governed parts of present-day Karnataka in southern India.
-
E.
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.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773f8f688190b616f972b9bbb28e |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:18 a.m.