Triple

T15876368
Position Surface form Disambiguated ID Type / Status
Subject Rakhine State E384961 entity
Predicate hasRiver P165 FINISHED
Object Mayu 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: Mayu River | Statement: [Rakhine State, hasRiver, Mayu River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mayu River
Context triple: [Rakhine State, hasRiver, Mayu River]
  • A. Mayu River chosen
    The Mayu River is a river in western Myanmar’s Rakhine State that flows into the Bay of Bengal near the coastal city of Sittwe.
  • B. Taiya River
    The Taiya River is a glacially fed river in Southeast Alaska that flows through the historic Klondike Gold Rush region near Skagway before emptying into the Taiya Inlet.
  • C. Tenma River
    The Tenma River is a distributary waterway that branches from the Ōta River in Hiroshima, Japan, forming part of the city’s river delta network.
  • D. Yuruari River
    The Yuruari River is a tributary waterway in southeastern Venezuela that feeds into the Caroní River within the Guiana Shield region.
  • E. Misa River
    The Misa River is a watercourse in Italy’s Marche region that flows through the town of Senigallia before reaching the Adriatic Sea.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fdc1b881909d1c82c4c66a195a completed April 16, 2026, 9:34 p.m.
Created at: April 10, 2026, 4:51 a.m.