Triple

T6210279
Position Surface form Disambiguated ID Type / Status
Subject Tulsi Manas Mandir E138848 entity
Predicate hasDeity P5606 FINISHED
Object Rama E103308 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: Rama | Statement: [Tulsi Manas Mandir, hasDeity, Rama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rama
Context triple: [Tulsi Manas Mandir, hasDeity, Rama]
  • A. Rama
    Rama is a small scenic village in Pakistan’s Gilgit-Baltistan region, known as a gateway to the lush Rama Meadows and views of Nanga Parbat.
  • B. Rama chosen
    Rama is a major Hindu deity and the virtuous prince-king of Ayodhya, revered as the seventh avatar of Vishnu and hero of the epic Ramayana.
  • C. Ramachandra
    Ramachandra, better known as Tatya Tope, was a prominent Indian general and key leader of the 1857 Indian Rebellion against British rule.
  • D. Ramachandra
    Ramachandra is a common Indian male given name of Sanskrit origin, often associated with the Hindu deity Lord Rama.
  • E. Vibhishana
    Vibhishana is a virtuous rakshasa prince in the Hindu epic Ramayana, known for abandoning his brother Ravana to ally with Rama and uphold dharma.
  • 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_69c008ada364819096c9e92c74d639b5 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062896f3881909f264bb45badc5d0 completed March 22, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c20da55e3c81909a61471b38e88894 completed March 24, 2026, 4:05 a.m.
Created at: March 22, 2026, 4:21 p.m.