Triple

T16382179
Position Surface form Disambiguated ID Type / Status
Subject Susitna Valley E397832 entity
Predicate hasRiver P165 FINISHED
Object Yentna River E531677 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: Yentna River | Statement: [Susitna Valley, hasRiver, Yentna River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yentna River
Context triple: [Susitna Valley, hasRiver, Yentna River]
  • A. Yentna River chosen
    The Yentna River is a major glacial-fed river in south-central Alaska that flows through remote wilderness before joining the Susitna River.
  • B. Tuluksak River
    The Tuluksak River is a waterway in southwestern Alaska that serves as an important tributary of the Kuskokwim River and a natural resource for nearby communities.
  • C. Koyuk River
    The Koyuk River is a waterway in western Alaska that flows into Norton Sound on the Bering Sea.
  • D. Aniak River
    The Aniak River is a significant waterway in western Alaska that flows into the Kuskokwim River and supports local communities, subsistence activities, and salmon fisheries.
  • E. Chickaloon River
    Chickaloon River is a tributary stream in southcentral Alaska that feeds into the Matanuska River and flows through a largely remote, mountainous landscape.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319dd0e0c8190812bde6a2f7d9644 completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00aae394d48190aca8e6f5e1cc781f completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:08 a.m.