Triple

T25778146
Position Surface form Disambiguated ID Type / Status
Subject Thwaites Glacier E649210 entity
Predicate seaLevelRiskTimeScale P8806 FINISHED
Object centuries 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: centuries | Statement: [Thwaites Glacier, seaLevelRiskTimeScale, centuries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seaLevelRiskTimeScale
Context triple: [Thwaites Glacier, seaLevelRiskTimeScale, centuries]
  • A. hasRiskLevelComparedToNearbySea
    Indicates the relative level of risk an entity has when compared to the nearby sea, such as in terms of exposure, danger, or vulnerability.
  • B. seaLevelCharacteristic chosen
    Indicates a characteristic, property, or attribute specifically related to sea level.
  • C. geologicHazardLevel
    Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
  • D. waterLevelRise
    Indicates that the level of water in a given area or container has increased over time.
  • E. hasCoastalRisk
    Indicates that an entity is exposed to potential hazards or adverse impacts associated with coastal environments, such as flooding, erosion, or storm surge.
  • 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_69e7ab333b508190b6d708d8d9a328ed completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fe5e7d3481908a77848582404490 completed May 2, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69f4938b960081909b53c074a3e0c7c2 completed May 1, 2026, 11:50 a.m.
Created at: April 22, 2026, 5:35 a.m.