Triple

T22352245
Position Surface form Disambiguated ID Type / Status
Subject Neemuch district E552561 entity
Predicate hasMajorTown P316 FINISHED
Object Manasa 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: Manasa | Statement: [Neemuch district, hasMajorTown, Manasa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manasa
Context triple: [Neemuch district, hasMajorTown, Manasa]
  • A. Manasa
    Manasa is a Hindu serpent goddess primarily worshipped in eastern India as a protector against snakebites and a granter of fertility and prosperity.
  • B. Manasa chosen
    Manasa is a town in the Malwa region of Madhya Pradesh, India, known as a local commercial and administrative center.
  • C. Saubhadra
    Saubhadra is a renowned Marathi musical play (sangeet natak) by Annasaheb Kirloskar, celebrated as a classic of 19th-century Indian theatre.
  • D. Kshipra
    Kshipra is a sacred river in central India, best known for flowing through the holy city of Ujjain and its importance in Hindu religious traditions and festivals.
  • 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 (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_69e11e4a0ad08190a385b4d343cf6524 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1579cbbe88190bf2f27d34fc8f30e completed April 29, 2026, 12:58 a.m.
Created at: April 16, 2026, 8:44 p.m.