Triple

T10713085
Position Surface form Disambiguated ID Type / Status
Subject Nizamabad district E252588 entity
Predicate containsTown P847 FINISHED
Object Bodhan E881039 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: Bodhan | Statement: [Nizamabad district, containsTown, Bodhan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodhan
Context triple: [Nizamabad district, containsTown, Bodhan]
  • A. Bodhan chosen
    Bodhan is a town and municipal center in the Nizamabad district of Telangana, India, known historically for its sugar industry and regional trade.
  • B. Gurgum
    Gurgum was an Iron Age Neo-Hittite kingdom located in southeastern Anatolia, known from Assyrian records for its regional political and military significance.
  • C. Ratho
    Ratho is a village in Edinburgh, Scotland, known for its historic canal-side setting and proximity to the Edinburgh International Climbing Arena.
  • D. Tathra
    Tathra is a coastal town on the Sapphire Coast of New South Wales, Australia, known for its historic wharf, scenic beaches, and fishing.
  • E. Besnagar
    Besnagar is the ancient name of the historic city of Vidisha in central India, known for its archaeological remains and significance in early Indian history.
  • 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_69d6aa5cbabc8190973e683950d89faf completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fe54465081909640f6d7a2314fcb completed April 9, 2026, 1:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69dbb70f67c88190980f362fcea9d800 completed April 12, 2026, 3:15 p.m.
Created at: April 8, 2026, 9:13 p.m.