Triple

T23494612
Position Surface form Disambiguated ID Type / Status
Subject Ganjam district E571668 entity
Predicate hasTown P847 FINISHED
Object Kabisuryanagar 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: Kabisuryanagar | Statement: [Ganjam district, hasTown, Kabisuryanagar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kabisuryanagar
Context triple: [Ganjam district, hasTown, Kabisuryanagar]
  • A. Kabisuryanagar chosen
    Kabisuryanagar is a town in the Indian state of Odisha known for its local markets, educational institutions, and role as a regional commercial center.
  • B. Mahendranagar
    Mahendranagar is a major city in far‑western Nepal, serving as an important commercial and administrative hub near the Indian border.
  • C. Shyamnagar
    Shyamnagar is a suburban locality in West Bengal, India, situated along the Sealdah–Ranaghat railway corridor and forming part of the greater Kolkata metropolitan region.
  • D. Brajarajnagar
    Brajarajnagar is a town in the Jharsuguda district of Odisha, India, known historically for its paper and industrial enterprises.
  • E. Krishnanagar
    Krishnanagar is a historic town in eastern India known for its cultural heritage, temples, and traditional clay artistry.
  • 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_69e245b4829881909b77a70e942bbd54 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a7def8ac8190ade511299078d55b completed April 29, 2026, 6:40 a.m.
Created at: April 17, 2026, 6:05 p.m.