Triple

T2585074
Position Surface form Disambiguated ID Type / Status
Subject Battle of Khadki E57179 entity
Predicate location P40 FINISHED
Object Khadki E183687 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: Khadki | Statement: [Battle of Khadki, location, Khadki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khadki
Context triple: [Battle of Khadki, location, Khadki]
  • A. Khadki chosen
    Khadki is the historical name of the Indian city now known as Aurangabad in Maharashtra.
  • B. Dhatki
    Dhatki is an Indo-Aryan language variety spoken primarily in parts of Rajasthan, India, and neighboring regions of Pakistan, often considered a dialect within the broader Rajasthani language continuum.
  • C. Dhundhari
    Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
  • D. Kanchrapara
    Kanchrapara is a town in the North 24 Parganas district of West Bengal, India, known historically for its railway workshop and suburban connectivity to Kolkata.
  • E. Kadamtala
    Kadamtala is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • 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_69ab4a4dca6481908c301f8e317396e7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3cd07588190b3cb8cc348f12938 completed March 7, 2026, 7:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69af6581f6fc819099ea28ecbb0093d7 completed March 10, 2026, 12:27 a.m.
Created at: March 6, 2026, 9:49 p.m.