Triple

T13895333
Position Surface form Disambiguated ID Type / Status
Subject Kosal region E334072 entity
Predicate hasMajorCity P316 FINISHED
Object Balangir E821290 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: Balangir | Statement: [Kosal region, hasMajorCity, Balangir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balangir
Context triple: [Kosal region, hasMajorCity, Balangir]
  • A. Balangir chosen
    Balangir is a town and district in the western Indian state of Odisha, known as a cultural center of the Kosal (Koshali) region.
  • B. Sambalpur
    Sambalpur is a historic city and former princely region in western Odisha, India, known for its cultural heritage, textile traditions, and role in 19th-century colonial-era political events.
  • C. Bargarh
    Bargarh is a town and district in the Indian state of Odisha, known for its agricultural economy and rich regional culture.
  • D. Chakradharpur
    Chakradharpur is a key railway town in Jharkhand, India, serving as an important divisional headquarters and transport hub on the Indian Railways network.
  • E. Sundargarh district
    Sundargarh district is a mineral-rich district in the Indian state of Odisha, known for its major industrial and mining activities centered around the city of Rourkela.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a741908190bdf46d76c5f1411a completed April 14, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe7e72b9f08190a33e8e20541edd21 completed May 9, 2026, 12:23 a.m.
Created at: April 9, 2026, 10:15 p.m.