Triple

T24335547
Position Surface form Disambiguated ID Type / Status
Subject Fox Glacier E613368 entity
Predicate accessModeToLowerGlacier P6529 FINISHED
Object primarily by helicopter for guided parties 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: primarily by helicopter for guided parties | Statement: [Fox Glacier, accessModeToLowerGlacier, primarily by helicopter for guided parties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessModeToLowerGlacier
Context triple: [Fox Glacier, accessModeToLowerGlacier, primarily by helicopter for guided parties]
  • A. hasGlacierAccess
    Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
  • B. accessMode chosen
    Indicates the manner or method by which an entity can be accessed, used, or interacted with.
  • C. standardApproachGlacier
    Indicates a glacier that is typically used as the main or customary route of approach to a mountain or climbing objective.
  • D. accessRole
    Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
  • E. hasGlacier
    Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
  • 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_69e2d7dcc5a08190b53691130d56cbc4 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f292f5346881909ca93b7ceef543ed completed April 29, 2026, 11:23 p.m.
PD Predicate disambiguation batch_69f287ad30048190b3ad3613486f277f completed April 29, 2026, 10:35 p.m.
Created at: April 18, 2026, 1:56 a.m.