Triple

T18836025
Position Surface form Disambiguated ID Type / Status
Subject Ujjain division E460666 entity
Predicate containsCity P294 FINISHED
Object Neemuch 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: Neemuch | Statement: [Ujjain division, containsCity, Neemuch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neemuch
Context triple: [Ujjain division, containsCity, Neemuch]
  • A. Neemuch chosen
    Neemuch is a town in northwestern Madhya Pradesh, India, known as an important agricultural and trading center and for hosting a significant military cantonment.
  • B. Samastipur
    Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
  • C. Jabalpur
    Jabalpur is a major city in the central Indian state of Madhya Pradesh, known for its industrial base, educational institutions, and nearby marble rock formations along the Narmada River.
  • D. Hajipur
    Hajipur is a prominent city in the Indian state of Bihar, known as an important railway and commercial hub located near the state capital, Patna.
  • E. Sonepur
    Sonepur is a prominent town in western Odisha, India, known for its cultural heritage and historical significance within the Kosal region.
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5a99d491c81909d8e55ac45621d44 completed April 20, 2026, 4:20 a.m.
Created at: April 10, 2026, 11:56 a.m.