Triple

T11444308
Position Surface form Disambiguated ID Type / Status
Subject Amarkantak E271224 entity
Predicate hasTemple P1191 FINISHED
Object Shri Yantra Mandir E927075 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: Shri Yantra Mandir | Statement: [Amarkantak, hasTemple, Shri Yantra Mandir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shri Yantra Mandir
Context triple: [Amarkantak, hasTemple, Shri Yantra Mandir]
  • A. Shri Yantra Mandir chosen
    Shri Yantra Mandir is a Hindu temple at Teerthraj Amarkantak dedicated to the worship of the Shri Yantra, a sacred geometric representation of the goddess Tripura Sundari and cosmic energy.
  • B. Santram Mandir
    Santram Mandir is a prominent Hindu temple and spiritual center renowned as a major pilgrimage site in Nadiad, Gujarat, India.
  • C. Gaon Mandir
    Gaon Mandir is a Jain temple located in Pavapuri, a significant pilgrimage site associated with Lord Mahavira.
  • D. Mai Mandir
    Mai Mandir is a prominent Hindu temple in Nadiad, Gujarat, known for its distinctive architecture and religious significance to local devotees.
  • E. Durga Mandir
    Durga Mandir is a prominent Hindu temple in Varanasi dedicated to the goddess Durga, known for its religious significance and distinctive red-colored architecture.
  • 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_69d6aadff8888190a13f253f0d460874 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8088a66f48190b2b4a56cd62097cf completed April 9, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69e624782cf88190b696a1c7c9a56395 completed April 20, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:35 p.m.