Triple

T4906629
Position Surface form Disambiguated ID Type / Status
Subject Devas E109926 entity
Predicate opposedTo P437 FINISHED
Object Asuras E448889 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: Asuras | Statement: [Devas, opposedTo, Asuras]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asuras
Context triple: [Devas, opposedTo, Asuras]
  • A. Asura chosen
    Asura is a class of powerful, often antagonistic supernatural beings in Indian religions, particularly Hinduism and Buddhism, frequently depicted as rivals of the gods (Devas).
  • B. Rakshasas
    Rakshasas are powerful, shape-shifting demon beings from Hindu mythology, often portrayed as malevolent antagonists in epics like the Ramayana.
  • C. Devas
    The Devas are celestial gods in Hindu mythology who play pivotal roles in the cosmic order and divine interventions depicted throughout the Ramayana.
  • D. Vanaras
    Vanaras are a race of monkey-like humanoid warriors in the Indian epic Ramayana, renowned for their strength, agility, and pivotal role in aiding Rama in his quest to rescue Sita.
  • E. Horkos
    Horkos is the personification of oaths and the curse that falls upon those who break them in Greek mythology.
  • 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_69bd441180708190ba42ffb44fea533a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e72ed5c819081104c99a398e0af completed March 20, 2026, 3:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6fdd89588190ae9c8de779d89aaf completed March 21, 2026, 10:15 a.m.
Created at: March 20, 2026, 1:29 p.m.