Triple

T14512476
Position Surface form Disambiguated ID Type / Status
Subject Xabûr E340431 entity
Predicate refersTo P37 FINISHED
Object Khabur 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: Khabur River | Statement: [Xabûr, refersTo, Khabur River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khabur River
Context triple: [Xabûr, refersTo, Khabur River]
  • A. Khabur River chosen
    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.
  • B. Khan River
    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.
  • 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. Bhera River
    The Bhera River is a significant tributary watercourse that feeds into eastern India’s Damodar River system.
  • E. Tamur River
    The Tamur River is a major river in eastern Nepal that originates near the Kanchenjunga region and joins other rivers to form part of the Kosi River system flowing into India.
  • 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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69de9a6c6054819086b4c0ce1d83fdc5 completed April 14, 2026, 7:50 p.m.
Created at: April 10, 2026, 1:21 a.m.