Triple

T5375638
Position Surface form Disambiguated ID Type / Status
Subject Sringeri Sharada Peetham E108952 entity
Predicate hasDeity P5606 FINISHED
Object Sharada E487624 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: Sharada | Statement: [Sringeri Sharada Peetham, hasDeity, Sharada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sharada
Context triple: [Sringeri Sharada Peetham, hasDeity, Sharada]
  • A. Sharada
    Sharada is a Unicode block that encodes the historic Brahmic script once used for writing Sanskrit and Kashmiri in the northwestern regions of the Indian subcontinent.
  • B. Sharada chosen
    Sharada is a revered Hindu goddess of learning, wisdom, and the arts, often associated with Saraswati and worshipped as the presiding deity of the Dvaraka Sharada Peetham.
  • C. Dasharathi
    Dasharathi is an epithet of the Hindu deity Rama, highlighting him as the son of King Dasharatha.
  • D. Yajnaseni
    Yajnaseni is another name for Draupadi, the central heroine of the Indian epic Mahabharata, renowned for her strength, devotion, and pivotal role in the Kurukshetra war.
  • E. Vasusena
    Vasusena is the original birth name of Karna, a central warrior figure in the Indian epic Mahabharata.
  • 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_69bd440c77948190aad2a5f39b7b80f5 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd86aed2a8819089d9e699f53563db completed March 20, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf293f6458819091c32080782b56ed completed March 21, 2026, 11:26 p.m.
Created at: March 20, 2026, 2:03 p.m.