Triple

T17701006
Position Surface form Disambiguated ID Type / Status
Subject Panj River E441298 entity
Predicate hasNameVariant P457 FINISHED
Object Pyanj 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: Pyanj River | Statement: [Panj River, hasNameVariant, Pyanj River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyanj River
Context triple: [Panj River, hasNameVariant, Pyanj River]
  • A. Pyanj River chosen
    Pyanj River is a major river in Central Asia that forms much of the border between Tajikistan and Afghanistan and serves as an important tributary of the Amu Darya.
  • B. Tshuapa River
    The Tshuapa River is a significant waterway in the Democratic Republic of the Congo that drains the central rainforest region and contributes to the Congo River basin.
  • C. Tanyurer River
    The Tanyurer River is a significant watercourse in Russia’s Far East that feeds into the larger Anadyr River system.
  • D. Kwisa River
    The Kwisa River is a river in southwestern Poland that flows through the historical region of Lower Silesia before joining the Bóbr River.
  • E. Nyamiha River
    The Nyamiha River is a small, historically significant waterway in Minsk, Belarus, now largely confined to underground culverts beneath the city.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715ae1fc81908438a1bba970c6ec completed April 19, 2026, 6:08 a.m.
Created at: April 10, 2026, 10:04 a.m.