Triple

T26921967
Position Surface form Disambiguated ID Type / Status
Subject Noorvik E677670 entity
Predicate hasRiverCulture P168070 FINISHED
Object Kobuk 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: Kobuk River | Statement: [Noorvik, hasRiverCulture, Kobuk River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRiverCulture
Context triple: [Noorvik, hasRiverCulture, Kobuk River]
  • A. hasRiverValley
    Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
  • B. hasRiverValleyType
    Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
  • C. associatedWithRiverValleyCivilization
    Indicates that there is a connection or relevance between something and a specific river valley civilization, such as through origin, influence, location, or historical context.
  • D. hasCulturalLegacyIn
    Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
  • E. hasAncestralRiver
    Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
  • F. None of above. chosen

Provenance (4 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_69eee9bdebc48190ba90a12a63e09c73 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f673633d288190b52ceb9f8a057c44 completed May 2, 2026, 9:57 p.m.
PD Predicate disambiguation batch_69f66ec3d3d48190ab2f2b71939e572e completed May 2, 2026, 9:38 p.m.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 27, 2026, 6:07 a.m.