Triple

T21889861
Position Surface form Disambiguated ID Type / Status
Subject Kelani Ganga E540509 entity
Predicate hasTributary P415 FINISHED
Object Maskeli Oya 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: Maskeli Oya | Statement: [Kelani Ganga, hasTributary, Maskeli Oya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maskeli Oya
Context triple: [Kelani Ganga, hasTributary, Maskeli Oya]
  • A. Maskeliya Oya chosen
    Maskeliya Oya is a river in central Sri Lanka that flows through the hill country and feeds into the Kelani River basin.
  • B. Yesan
    Yesan is an alternate name for the Tutelo language, a nearly extinct Siouan language historically spoken by the Tutelo people of eastern North America.
  • C. Shinar
    Shinar is an ancient biblical region, often associated with Mesopotamia and the setting of narratives such as the Tower of Babel.
  • D. Okyar
    Okyar is a Turkish surname most notably associated with Fethi Okyar, an important early 20th-century Turkish statesman and diplomat.
  • E. Yarden
    Yarden is the Hebrew name for the Jordan River, a historically and religiously significant river in the Middle East.
  • 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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118ef2b648190bbd78f6b3958d2ee completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:06 p.m.