Triple

T18734439
Position Surface form Disambiguated ID Type / Status
Subject Barakar River E458123 entity
Predicate flowsNear P350 FINISHED
Object Koderma NE NERFINISHED

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: Koderma | Statement: [Barakar River, flowsNear, Koderma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koderma
Context triple: [Barakar River, flowsNear, Koderma]
  • A. Giridih
    Giridih is a city in eastern India known for its coal and mica mining, situated in the Giridih district of the state of Jharkhand.
  • B. Daltonganj
    Daltonganj, now officially known as Medininagar, is a town in the Palamu district of Jharkhand, India, serving as an important regional administrative and commercial center.
  • C. Koderma district chosen
    Koderma district is an administrative district in the Indian state of Jharkhand, known for its rich mica deposits and predominantly rural population.
  • D. Chaibasa
    Chaibasa is a town in eastern India that serves as the administrative headquarters of West Singhbhum district in the state of Jharkhand.
  • E. Bilaspur
    Bilaspur is a town in the Yamunanagar district of Haryana, India, known as a local commercial and administrative center for surrounding rural areas.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d393ba9c8190a8b03b04ddbb0a09 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56d7a06788190a8e09c657aaeb8e5 completed April 20, 2026, 12:04 a.m.
Created at: April 10, 2026, 11:51 a.m.