Triple

T1609689
Position Surface form Disambiguated ID Type / Status
Subject Rawal Lake E34588 entity
Predicate outflow P967 FINISHED
Object Korang River E390813 NE FINISHED

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: Korang River | Statement: [Rawal Lake, outflow, Korang River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korang River
Context triple: [Rawal Lake, outflow, Korang River]
  • A. Korang River chosen
    Korang River is a stream in Pakistan that serves as a primary inflow to Rawal Lake near Islamabad.
  • B. Merkys River
    The Merkys River is a significant river in southern Lithuania and northeastern Belarus, known for its scenic valleys and role in regional ecosystems before joining the Neman.
  • C. Warta River
    The Warta River is a major river in western and central Poland, flowing through cities such as Poznań before joining the Oder River.
  • D. Nyari River
    The Nyari River is a regional river in the Indian state of Gujarat that flows through and helps sustain the city of Rajkot.
  • E. Styr River
    The Styr River is a waterway in western Ukraine that flows through the city of Lutsk and is a tributary of the Pripyat River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa622a84548190a66d45eec70f9b85 completed March 6, 2026, 5:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69b511ebd11c8190ba5a6917d3731de9 completed March 14, 2026, 7:44 a.m.
Created at: March 4, 2026, 7:28 p.m.