Triple

T17979987
Position Surface form Disambiguated ID Type / Status
Subject Pulastya E449574 entity
Predicate relatedTo P37 FINISHED
Object Vishrava 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: Vishrava | Statement: [Pulastya, relatedTo, Vishrava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vishrava
Context triple: [Pulastya, relatedTo, Vishrava]
  • A. Vishrava chosen
    Vishrava is a revered sage in Hindu mythology, best known as the father of the demon king Ravana and his giant brother Kumbhakarna in the Ramayana.
  • B. Angaraja
    Angaraja is an epithet of Karna, the legendary warrior king from the Indian epic Mahabharata renowned for his valor, loyalty, and tragic fate.
  • C. Navakasiga
    Navakasiga is a village-level settlement located in the Bua Province on the northern island of Vanua Levu in Fiji.
  • D. Vrushabhadri
    Vrushabhadri is one of the sacred hills of the Tirumala range associated with the Tirumala Venkateswara Temple in Andhra Pradesh, India.
  • E. Gunabhadra
    Gunabhadra was a prominent Jain poet and scholar associated with the Rashtrakuta dynasty, known for his significant contributions to medieval Indian religious and literary traditions.
  • 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_69d8b9f9927c8190a006110c8b996e61 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b202aab88190b44851808c75a848 completed April 19, 2026, 10:44 a.m.
Created at: April 10, 2026, 10:22 a.m.