Triple

T1089657
Position Surface form Disambiguated ID Type / Status
Subject Rajkot E24131 entity
Predicate historicalRegion P915 FINISHED
Object Kathiawar E171932 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: Kathiawar | Statement: [Rajkot, historicalRegion, Kathiawar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kathiawar
Context triple: [Rajkot, historicalRegion, Kathiawar]
  • A. Kathiawar chosen
    Kathiawar is a peninsula in western India, in present-day Gujarat, historically known for its princely states and coastal trade centers.
  • B. Kathiawari
    Kathiawari is a regional dialect of Gujarati spoken primarily in the Saurashtra (Kathiawar) peninsula of western India, known for its distinct phonetic and lexical features.
  • C. Bhind
    Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
  • D. Shivpuri
    Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
  • E. Jhabua
    Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
  • 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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b97f216881909e9b8943ce2078e4 completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad293450488190ac8a795524ca0c2c completed March 8, 2026, 7:45 a.m.
Created at: March 1, 2026, 7:42 p.m.