Triple

T18310537
Position Surface form Disambiguated ID Type / Status
Subject Dyea, Alaska E438612 entity
Predicate locatedOn P40 FINISHED
Object Taiya 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: Taiya River | Statement: [Dyea, Alaska, locatedOn, Taiya River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taiya River
Context triple: [Dyea, Alaska, locatedOn, Taiya River]
  • A. Taiya River chosen
    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.
  • B. 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.
  • C. Denwa River
    The Denwa River is a central waterway in central India that flows through the Satpura region, supporting the rich wildlife and ecosystems of Satpura National Park.
  • D. Dokawa River
    Dokawa River is a river flowing through the city of Fukuchiyama in Kyoto Prefecture, Japan.
  • E. Iori River
    The Iori River is a river in the South Caucasus that flows through eastern Georgia and parts of Azerbaijan before joining the Kura (Mtkvari) River.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e502180d208190ae7c4f3d0ef3dc55 completed April 19, 2026, 4:26 p.m.
Created at: April 10, 2026, 10:36 a.m.