Triple

T17938367
Position Surface form Disambiguated ID Type / Status
Subject Gaura Purnima E448525 entity
Predicate associatedPlace P1481 FINISHED
Object Navadvipa 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: Navadvipa | Statement: [Gaura Purnima, associatedPlace, Navadvipa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Navadvipa
Context triple: [Gaura Purnima, associatedPlace, Navadvipa]
  • A. Navadvipa chosen
    Navadvipa is a historic town in West Bengal, India, revered as a major center of Gaudiya Vaishnavism and the birthplace region of the saint Chaitanya Mahaprabhu.
  • B. Pavapuri
    Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
  • C. Haladhara
    Haladhara is another name for the Hindu deity Balarama, revered as Krishna’s elder brother and famed for wielding the plough as his primary weapon.
  • D. Kishkindha
    Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
  • E. Varuṇaloka
    Varuṇaloka is the mythological celestial realm associated with the Vedic deity Varuna, often envisioned as his divine oceanic or watery domain.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad9455fc81908bf595f9ed42c624 completed April 19, 2026, 10:25 a.m.
Created at: April 10, 2026, 10:21 a.m.