Triple

T21142803
Position Surface form Disambiguated ID Type / Status
Subject Gujarat princely states E520974 entity
Predicate includedState P11085 FINISHED
Object Kutch State 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: Kutch State | Statement: [Gujarat princely states, includedState, Kutch State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kutch State
Context triple: [Gujarat princely states, includedState, Kutch State]
  • A. Kutch chosen
    Kutch is a large district in western India known for its salt desert landscapes, rich handicraft traditions, and vibrant cultural festivals.
  • B. Santrampur State
    Santrampur State was a former princely state in British India, located in what is now the state of Gujarat.
  • C. Palanpur State
    Palanpur State was a former princely state in western India, located in present-day Gujarat and ruled by the Palanpur Nawabs under British suzerainty until independence.
  • D. Jhabua State
    Jhabua State was a former princely state in western India, located in what is now Madhya Pradesh and historically ruled by Rajput chiefs under British suzerainty.
  • E. Narsinghgarh State
    Narsinghgarh State was a former princely state in central India, historically ruled by local royalty under British suzerainty.
  • 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_69e0b50c6a848190a4e525a77a319b8a completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e723fad02c8190a8e9fb82f0491642 completed April 21, 2026, 7:15 a.m.
Created at: April 16, 2026, 2:57 p.m.