Triple

T31255792
Position Surface form Disambiguated ID Type / Status
Subject Swiftcurrent Glacier E796965 entity
Predicate hasParkRegion P57709 FINISHED
Object Many Glacier region of Glacier National Park 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: Many Glacier region of Glacier National Park | Statement: [Swiftcurrent Glacier, hasParkRegion, Many Glacier region of Glacier National Park]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasParkRegion
Context triple: [Swiftcurrent Glacier, hasParkRegion, Many Glacier region of Glacier National Park]
  • A. hasParkDistrict
    Indicates that an entity is associated with, located within, or administered by a specific park district.
  • B. hasParkArea
    Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
  • C. hasParkSection chosen
    Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
  • D. hasParkStatus
    Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
  • E. hasParkAccess
    Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
  • 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_69f224dd5fdc81908a4cd24917b67668 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe991bca608190b524e419642f4243 completed May 9, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69fe979fc1c4819091fc48d63ea12063 completed May 9, 2026, 2:10 a.m.
Created at: April 29, 2026, 9:12 p.m.