Triple

T5844924
Position Surface form Disambiguated ID Type / Status
Subject Baghelkhand E129684 entity
Predicate containsCity P294 FINISHED
Object Satna E111450 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: Satna | Statement: [Baghelkhand, containsCity, Satna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Satna
Context triple: [Baghelkhand, containsCity, Satna]
  • A. Satna chosen
    Satna is a prominent industrial and commercial city in central India, known especially for its large cement factories and strategic location in Madhya Pradesh.
  • B. Sabni
    Sabni was an ancient Egyptian official from the Old Kingdom whose rock-cut tomb at Aswan’s Tombs of the Nobles is notable for its detailed inscriptions and scenes illustrating his life and status.
  • C. Sarabha
    Sarabha is an Indian surname most notably associated with Kartar Singh Sarabha, a prominent revolutionary in the Indian independence movement.
  • D. Salbai
    Salbai is a historical location in India known primarily as the site where the 1782 Treaty of Salbai was concluded between the British East India Company and the Maratha Empire.
  • E. Maddur
    Maddur is a town in Karnataka, India, known for its location between Bengaluru and Mysuru and its popular local snack, Maddur vada.
  • 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_69c0084bd31c8190a796bb6284845e83 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c034dcafe88190a438034a539ffa52 completed March 22, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a1a9ffa881908b38eeddb411c4ab completed March 23, 2026, 2:12 a.m.
Created at: March 22, 2026, 3:55 p.m.