Triple

T15648316
Position Surface form Disambiguated ID Type / Status
Subject Lakhpat E376237 entity
Predicate culturalRegion P1968 FINISHED
Object Kutch E76150 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: Kutch | Statement: [Lakhpat, culturalRegion, Kutch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kutch
Context triple: [Lakhpat, culturalRegion, Kutch]
  • 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. Kutchi
    Kutchi is an Indo-Aryan language spoken primarily by the Kutchi people of the Kutch region in the Indian state of Gujarat and in diaspora communities abroad.
  • C. Sirohi
    Sirohi is a town in the Indian state of Rajasthan known for its historical significance and role as the former seat of a princely state.
  • D. 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.
  • E. Ratlam State
    Ratlam State was a princely state in British India, located in the Malwa region of present-day Madhya Pradesh and ruled by a dynasty of Rathore Rajputs.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed7212c8190be6ff76afa25f7ca completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff908b1d6c819086441305b55f81fb completed May 9, 2026, 7:52 p.m.
Created at: April 10, 2026, 4:15 a.m.