Triple

T3687949
Position Surface form Disambiguated ID Type / Status
Subject Kheda district E78270 entity
Predicate hasTown P847 FINISHED
Object Kapadvanj E365454 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: Kapadvanj | Statement: [Kheda district, hasTown, Kapadvanj]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kapadvanj
Context triple: [Kheda district, hasTown, Kapadvanj]
  • A. Kapadvanj chosen
    Kapadvanj is a historic town in the Kheda district of Gujarat, India, known for its traditional markets and regional cultural heritage.
  • B. Titagarh
    Titagarh is an industrial town in the North 24 Parganas district of eastern India, known historically for its jute mills and proximity to Kolkata.
  • C. Khajauli
    Khajauli is a town located in the Madhubani district of the Indian state of Bihar.
  • D. Mukteshwar
    Mukteshwar is a scenic hill town in Uttarakhand, India, known for its panoramic Himalayan views, fruit orchards, and tranquil forests.
  • E. Baghat
    Baghat was a small princely state in colonial India that was incorporated into British-controlled territory during the 19th century.
  • 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_69ad85e285a081908f8cbfa9e2ed9b75 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4c960788190b73ede08658846aa completed March 8, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4c3c10f6481908feed99cddc56d47 completed March 14, 2026, 2:11 a.m.
Created at: March 8, 2026, 3:26 p.m.