Triple

T7730775
Position Surface form Disambiguated ID Type / Status
Subject Hanumangarh district E175245 entity
Predicate hasMajorTown P316 FINISHED
Object Hanumangarh E685215 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: Hanumangarh | Statement: [Hanumangarh district, hasMajorTown, Hanumangarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanumangarh
Context triple: [Hanumangarh district, hasMajorTown, Hanumangarh]
  • A. Hanumangarh chosen
    Hanumangarh is a town in the northern Indian state of Rajasthan, known for serving as an administrative and commercial center near the Ghaggar River and the Punjab border.
  • B. Deogarh
    Deogarh was a historic kingdom ruled by the Gonds, an indigenous community in central India.
  • C. Naraingarh
    Naraingarh is a town in the northern Indian state of Haryana, known for its agricultural surroundings and role as a local commercial center.
  • D. 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.
  • E. Hanuman Garhi
    Hanuman Garhi is a prominent hilltop temple in Ayodhya dedicated to Lord Hanuman, revered as one of the city's most important pilgrimage sites.
  • 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_69c6995e912c81909a49a2657103f786 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c703358cf881909df8496d943d6de7 completed March 27, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8be3244088190be26dec90db9cfb3 completed March 29, 2026, 5:52 a.m.
Created at: March 27, 2026, 4:06 p.m.