Triple

T21245388
Position Surface form Disambiguated ID Type / Status
Subject Mahesana district E523593 entity
Predicate administrativeHeadquarters P62 FINISHED
Object Mehsana 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: Mehsana | Statement: [Mahesana district, administrativeHeadquarters, Mehsana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mehsana
Context triple: [Mahesana district, administrativeHeadquarters, Mehsana]
  • A. Mehsana chosen
    Mehsana is a prominent city in the Indian state of Gujarat, known for its dairy industry, oil and natural gas fields, and historical temples.
  • B. Malvan
    Malvan is a coastal town in Maharashtra, India, known for its beaches, seafood cuisine, and historic Sindhudurg Fort.
  • C. Malvani
    Malvani is an Indo-Aryan language variety spoken primarily in the Konkan coastal region of Maharashtra and Goa, closely related to Marathi and Konkani.
  • D. Aonla
    Aonla is a parliamentary constituency in Uttar Pradesh, India, known for its agricultural economy and political significance.
  • E. Okhla
    Okhla is a locality in South Delhi, India, known for its industrial areas, residential colonies, and proximity to the Yamuna River.
  • 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_69e0b513b89c81908b27147e91368db2 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73599e5548190ad70d2c2bfa9e919 completed April 21, 2026, 8:30 a.m.
Created at: April 16, 2026, 3:47 p.m.