Triple

T19734903
Position Surface form Disambiguated ID Type / Status
Subject Indore district E473952 entity
Predicate river P165 FINISHED
Object Khan River 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: Khan River | Statement: [Indore district, river, Khan River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khan River
Context triple: [Indore district, river, Khan River]
  • A. Khan River chosen
    The Khan River is a small river flowing through the city of Indore in the Indian state of Madhya Pradesh, historically significant but heavily affected by urban pollution.
  • B. Khabur River
    The Khabur River is a major river in northeastern Syria that flows through the Jazira region and is historically significant as part of ancient Mesopotamia’s irrigation and settlement network.
  • C. Khasa River
    The Khasa River is a seasonal river in northern Iraq that flows through the city of Kirkuk and serves as one of its main waterways.
  • D. Konar River
    The Konar River is a significant river in eastern India that flows through Jharkhand and is known for the Konar Dam, which supports irrigation and power generation in the region.
  • E. Bhera River
    The Bhera River is a significant tributary watercourse that feeds into eastern India’s Damodar River system.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515d138c8190a4c4d112ed5756a3 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.