Triple

T19814743
Position Surface form Disambiguated ID Type / Status
Subject Ranganatha E476031 entity
Predicate liesOn P3250 FINISHED
Object Adishesha 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: Adishesha | Statement: [Ranganatha, liesOn, Adishesha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adishesha
Context triple: [Ranganatha, liesOn, Adishesha]
  • A. Adishesha chosen
    Adishesha is the primordial cosmic serpent in Hindu mythology, often depicted as the multi-headed serpent on whom the god Vishnu reclines.
  • B. demon Tarakasura
    Tarakasura is a powerful demon king in Hindu mythology, best known for being slain by the god Kartikeya (Skanda) after receiving a boon that made him nearly invincible.
  • C. Mahishmati
    Mahishmati is a grand, fictional ancient Indian kingdom known as the central setting of the epic action film series "Baahubali."
  • D. Mahishasura
    Mahishasura is a powerful buffalo demon in Hindu mythology, best known as the formidable adversary slain by the goddess Durga in a legendary cosmic battle.
  • E. Bhurishravas
    Bhurishravas is a warrior prince from the Mahabharata epic, known as a formidable Kaurava ally who meets his end on the battlefield of Kurukshetra.
  • 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654f6495c81908e7eea359a60e40f completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.