Triple

T15302649
Position Surface form Disambiguated ID Type / Status
Subject Vøringsfossen E365825 entity
Predicate largestSingleDrop P118029 FINISHED
Object 145 m 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: 145 m | Statement: [Vøringsfossen, largestSingleDrop, 145 m]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: largestSingleDrop
Context triple: [Vøringsfossen, largestSingleDrop, 145 m]
  • A. largestSpan
    Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
  • B. maximumDraft
    Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
  • C. verticalDrop_ft
    Indicates the vertical distance, measured in feet, that one entity drops or falls relative to another reference level.
  • D. historicalPeak
    Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
  • E. maximumDischarge
    Indicates the greatest allowable or observed rate at which something can be discharged or released from a 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_69d85a113ee881908e297a1d38dd79fa completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03ccd575c8190aa43262d3b73ef3c completed April 16, 2026, 1:35 a.m.
PD Predicate disambiguation batch_69deca935e2c8190b640987ddfc542b9 completed April 14, 2026, 11:15 p.m.
PDg Predicate description generation batch_69decf2e413481909d9180a8d78d2c17 completed April 14, 2026, 11:35 p.m.
Created at: April 10, 2026, 3:15 a.m.