Triple

T7296322
Position Surface form Disambiguated ID Type / Status
Subject Nadia district E164529 entity
Predicate containsCity P294 FINISHED
Object Kalyani E184770 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: Kalyani | Statement: [Nadia district, containsCity, Kalyani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kalyani
Context triple: [Nadia district, containsCity, Kalyani]
  • A. Kalyani chosen
    Kalyani is a planned town in the Nadia district of West Bengal, India, known for its educational institutions, industries, and organized urban layout.
  • B. Bhagyanagar
    Bhagyanagar is an old historical name for the Indian city now known as Hyderabad.
  • C. Krishnanagar
    Krishnanagar is a historic town in eastern India known for its cultural heritage, temples, and traditional clay artistry.
  • D. Mahendranagar
    Mahendranagar is a major city in far‑western Nepal, serving as an important commercial and administrative hub near the Indian border.
  • E. Partapur
    Partapur is a locality in Meerut district of Uttar Pradesh, India, known for its proximity to the Dr. Bhimrao Ambedkar Airstrip and its growing urban and institutional development.
  • 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_69c6887a499881909dd23341399c59d8 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6eb8d0c6c8190b32cd08b9a5d96cc completed March 27, 2026, 8:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7e547c7b88190b792495efb3a215c completed March 28, 2026, 2:27 p.m.
Created at: March 27, 2026, 3 p.m.