Triple

T20901481
Position Surface form Disambiguated ID Type / Status
Subject Sudama Temple E514676 entity
Predicate associatedWith P37 FINISHED
Object Krishna 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: Krishna | Statement: [Sudama Temple, associatedWith, Krishna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krishna
Context triple: [Sudama Temple, associatedWith, Krishna]
  • A. Krishna
    Krishna is a major river in southern India that flows through the states of Maharashtra, Karnataka, Telangana, and Andhra Pradesh before emptying into the Bay of Bengal.
  • B. Krishna chosen
    Krishna is a major Hindu deity revered as the eighth avatar of Vishnu and celebrated for his roles as a divine lover, charioteer, and teacher in texts like the Bhagavad Gita and the Mahabharata.
  • C. Crishna
    Crishna is the family name of Smita Crishna-Godrej, a member of the prominent Indian industrialist Godrej family.
  • D. Krishnaa
    Krishnaa is another name for Draupadi, the central heroine of the Indian epic Mahabharata and wife of the five Pandava brothers.
  • E. Ramachandra
    Ramachandra is a common Indian male given name of Sanskrit origin, often associated with the Hindu deity Lord Rama.
  • 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_69e0b4f8a1108190bce3d31331290ced completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e8fc5d488190b62f51c35e768d38 completed April 21, 2026, 3:03 a.m.
Created at: April 16, 2026, 12:47 p.m.