Triple

T13127250
Position Surface form Disambiguated ID Type / Status
Subject Lake Missoula basin E311875 entity
Predicate maximumWaterVolume P13057 FINISHED
Object approximately 2,100 cubic kilometers 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: approximately 2,100 cubic kilometers | Statement: [Lake Missoula basin, maximumWaterVolume, approximately 2,100 cubic kilometers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumWaterVolume
Context triple: [Lake Missoula basin, maximumWaterVolume, approximately 2,100 cubic kilometers]
  • A. maximumHeightOfWaterJets
    Indicates the greatest vertical height that the water jets in a system or installation can reach.
  • B. maximumWaterDepth
    Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
  • C. maximumSurfaceArea
    Indicates that one entity has the greatest possible surface area among a set of comparable entities or under specified conditions.
  • D. waterVolume chosen
    Indicates the amount of water present in or associated with an entity, typically measured as a volume.
  • E. maximumMoundHeight
    Indicates the greatest allowable or observed height of a mound relative to a specified reference or context.
  • 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_69d806a9fe888190b081e2d9ea665d6c completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9819aac388190b59bf43cc6a49d0c completed April 10, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69d98043a74c81908648e6cd0b4c7f71 completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:07 p.m.