Triple

T33616451
Position Surface form Disambiguated ID Type / Status
Subject Hintereisferner E861130 entity
Predicate dataHostedBy P16030 FINISHED
Object World Glacier Monitoring Service NE NERFINISHED

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: World Glacier Monitoring Service | Statement: [Hintereisferner, dataHostedBy, World Glacier Monitoring Service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataHostedBy
Context triple: [Hintereisferner, dataHostedBy, World Glacier Monitoring Service]
  • A. hostedOn chosen
    Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
  • B. oftenHostedBy
    Indicates that an event, activity, or occurrence frequently takes place under the responsibility, organization, or auspices of a particular host.
  • C. hostingLocation
    Indicates the place or venue where an event, activity, or entity is being hosted or takes place.
  • D. hostedFrom
    Indicates that something (such as a service, application, or event) is provided, run, or made available starting from a particular location, source, or environment.
  • E. alsoHosted
    Indicates that the subject entity, in addition to others, served as a host for the same event or activity.
  • 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.