Triple

T9624890
Position Surface form Disambiguated ID Type / Status
Subject Umballa, British India E232434 entity
Predicate modernName P1213 FINISHED
Object Ambala E28747 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: Ambala | Statement: [Umballa, British India, modernName, Ambala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ambala
Context triple: [Umballa, British India, modernName, Ambala]
  • A. Ambala chosen
    Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
  • B. Saharanpur
    Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
  • C. Rohtak
    Rohtak is a major city in the Indian state of Haryana, known as an educational and administrative center within the National Capital Region.
  • D. Kaithal
    Kaithal is a historic town in the Indian state of Haryana, known for its medieval heritage and association with the Delhi Sultanate.
  • E. Muzaffarnagar
    Muzaffarnagar is a city in the Indian state of Uttar Pradesh, known as an agricultural and industrial center in the fertile Ganges-Yamuna Doab region.
  • 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_69ca848793ec8190a93a12383a754dc0 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9ad76b148190a38fadee06594db4 completed April 1, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69d189f7ea448190b9fe123589a9f3c5 completed April 4, 2026, 10 p.m.
Created at: March 30, 2026, 8:10 p.m.