Triple

T1335906
Position Surface form Disambiguated ID Type / Status
Subject Ambala E28747 entity
Predicate hasSubdivision P747 FINISHED
Object Ambala City E111346 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 City | Statement: [Ambala, hasSubdivision, Ambala City]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ambala City
Context triple: [Ambala, hasSubdivision, Ambala City]
  • A. Ambala
    Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
  • B. Ambala district chosen
    Ambala district is an administrative district in the northern Indian state of Haryana, known for its strategic location near the Punjab border and the city of Ambala, a major railway and military hub.
  • C. Faridabad
    Faridabad is a major industrial city in northern India known for its manufacturing sector and its location within the National Capital Region near New Delhi.
  • D. Yamunanagar
    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.
  • E. Moradabad
    Moradabad is a major city in northern India known for its brass handicraft industry and is located in the state of Uttar 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_69a498561a508190a3e1bc137c2b866a completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1ecb5208190a9eadda113c91e66 completed March 1, 2026, 10:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace56298708190819518926b2b608f completed March 8, 2026, 2:56 a.m.
Created at: March 1, 2026, 7:55 p.m.