Triple

T16930142
Position Surface form Disambiguated ID Type / Status
Subject Guria E410682 entity
Predicate hasRiver P165 FINISHED
Object Supsa 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: Supsa River | Statement: [Guria, hasRiver, Supsa River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Supsa River
Context triple: [Guria, hasRiver, Supsa River]
  • A. Supsa River chosen
    The Supsa River is a waterway in western Georgia that flows through the Guria region before emptying into the Black Sea.
  • B. Upía River
    The Upía River is a river in central Colombia that drains the waters of Lake Tota and flows eastward as part of the Orinoco River basin.
  • C. Tamsa River
    The Tamsa River is a tributary of the Ganges in northern India, flowing through Uttar Pradesh and Madhya Pradesh and passing towns such as Akbarpur along its course.
  • D. Livenza River
    The Livenza River is a northeastern Italian river that flows from the Alps through the regions of Friuli Venezia Giulia and Veneto before emptying into the Adriatic Sea.
  • E. Majes River
    The Majes River is a significant river in southern Peru known for irrigating the fertile Majes Valley and supporting extensive agricultural activities in an otherwise arid region.
  • 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_69d886c886688190967be07322597ac9 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cf248c6c81908fbf4d49e5381f08 completed April 18, 2026, 6:36 p.m.
Created at: April 10, 2026, 5:30 a.m.