Triple

T4216546
Position Surface form Disambiguated ID Type / Status
Subject Yamunanagar district E94230 entity
Predicate hasMajorTown P316 FINISHED
Object Yamunanagar E111942 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: Yamunanagar | Statement: [Yamunanagar district, hasMajorTown, Yamunanagar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yamunanagar
Context triple: [Yamunanagar district, hasMajorTown, Yamunanagar]
  • A. Yamunanagar chosen
    Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
  • B. Rampur
    Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
  • C. Rampur
    Rampur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known historically for its princely state heritage and distinctive Rampuri culture.
  • D. Jamnagar
    Jamnagar is a city in the Indian state of Gujarat, known for its oil refineries, brass industries, and proximity to the Gulf of Kutch.
  • E. Rewari
    Rewari is a historic city in the Indian state of Haryana, located near Delhi and known for its brass industry and strategic position in northern India.
  • 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_69b3451997e08190851db4a9a588837d completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34bea284081909beaded9873f0852 completed March 12, 2026, 11:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b76f07b4819097b59868af43b611 completed March 14, 2026, 7:30 p.m.
Created at: March 12, 2026, 11:04 p.m.