Triple

T4158444
Position Surface form Disambiguated ID Type / Status
Subject Karok E91471 entity
Predicate usesRiverFor P1477 FINISHED
Object fishing LITERAL 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: fishing | Statement: [Karok, usesRiverFor, fishing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesRiverFor
Context triple: [Karok, usesRiverFor, fishing]
  • A. hasRiver
    Indicates that a location or area contains, is traversed by, or is directly associated with a river.
  • B. reachedRiver
    Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
  • C. runOfTheRiver
    Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large reservoir.
  • D. hasRiverActivity chosen
    Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
  • E. isUrbanRiverOf
    Indicates that a river flows through or is located within an urban area associated with a specified place or city.
  • F. None of above.

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_69aed9626ebc8190a39de631788bea3e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0321eee88190871c1d4bf44a5007 completed March 9, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69af018dc90c8190a754b1bfbc802e80 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:44 p.m.