Triple

T33616435
Position Surface form Disambiguated ID Type / Status
Subject Hintereisferner E861130 entity
Predicate massBalanceMonitoringSince P70758 FINISHED
Object 1950s 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: 1950s | Statement: [Hintereisferner, massBalanceMonitoringSince, 1950s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: massBalanceMonitoringSince
Context triple: [Hintereisferner, massBalanceMonitoringSince, 1950s]
  • A. massBalanceTrend
    Indicates the direction and rate of change in the mass balance of a system (e.g., gaining, losing, or maintaining mass) over time.
  • B. massBalance
    Indicates that the total mass entering a system equals the total mass leaving or accumulating within it, reflecting conservation of mass.
  • C. hasMassBalance
    Indicates that one entity maintains or specifies the conservation and accounting of mass flows relative to another entity or system.
  • D. isMonitored chosen
    Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
  • E. monitoredFor
    Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
  • 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_69f34980fabc81909819228729a9ca84 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f817bc888190939e060506dca59a completed May 3, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69f6f6632dfc8190af85e258c8519207 completed May 3, 2026, 7:16 a.m.
Created at: May 1, 2026, 1:41 a.m.