Triple

T12386097
Position Surface form Disambiguated ID Type / Status
Subject Kolkata Metropolitan Area E295867 entity
Predicate containsCity P294 FINISHED
Object Titagarh E165051 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: Titagarh | Statement: [Kolkata Metropolitan Area, containsCity, Titagarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Titagarh
Context triple: [Kolkata Metropolitan Area, containsCity, Titagarh]
  • A. Titagarh chosen
    Titagarh is an industrial town in the North 24 Parganas district of eastern India, known historically for its jute mills and proximity to Kolkata.
  • B. Kheragarh
    Kheragarh is a town in the culturally significant Braj region of northern India, known for its historical and religious associations with the broader Mathura–Agra area.
  • C. Sujangarh
    Sujangarh is a town in the Indian state of Rajasthan known for its local markets, temples, and role as a regional commercial center.
  • D. Kishangarh
    Kishangarh is a town and legislative assembly constituency in Rajasthan, India, known for its marble industry and distinctive miniature paintings.
  • E. Dhupgarh
    Dhupgarh is the highest peak in the Satpura Range, located in the central Indian state of Madhya Pradesh.
  • 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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fbd489c819098233a111442762e completed April 10, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b926c5c81909427eb191ae75ec6 completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:54 p.m.