Triple

T18387103
Position Surface form Disambiguated ID Type / Status
Subject Little Missouri River (Arkansas) E446618 entity
Predicate hasFlowCharacteristic P8240 FINISHED
Object seasonally variable flow 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: seasonally variable flow | Statement: [Little Missouri River (Arkansas), hasFlowCharacteristic, seasonally variable flow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFlowCharacteristic
Context triple: [Little Missouri River (Arkansas), hasFlowCharacteristic, seasonally variable flow]
  • A. hasFlowRegime chosen
    Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
  • B. hasDirectionOfFlow
    Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
  • C. hasLiquidityCharacteristic
    Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
  • D. hasRiverineCharacteristic
    Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
  • E. hasFlowType
    Indicates the type or category of flow associated with or exhibited by an entity.
  • 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e517a114c08190af1be1ae52c83b63 completed April 19, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69e44ff1f92c8190afbb8e85d12bf2a9 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:46 a.m.