Triple

T35326935
Position Surface form Disambiguated ID Type / Status
Subject Crater Peak E1020211 entity
Predicate canAffectAviation P49069 FINISHED
Object yes 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: yes | Statement: [Crater Peak, canAffectAviation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canAffectAviation
Context triple: [Crater Peak, canAffectAviation, yes]
  • A. affectsAirTraffic chosen
    Indicates that one entity causes changes or disruptions to the normal flow, safety, or management of air traffic.
  • B. aircraftImpact
    Indicates that an aircraft collides with or crashes into a target or surface, causing an impact event.
  • C. isAviationElementFor
    Indicates that something serves as an aviation-related component, feature, or element specifically associated with or used for a particular object, system, or context.
  • D. rangeAgainstAircraft
    Indicates that one entity measures, determines, or engages the distance to an aircraft target.
  • E. hasGeneralAviationActivity
    Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
  • 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_69f76deacf4481908e7735a5a7715b0a completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f79533b88c8190934ec4cb21770e24 completed May 3, 2026, 6:34 p.m.
PD Predicate disambiguation batch_69f79104f5b48190a496cdffde8472da completed May 3, 2026, 6:16 p.m.
Created at: May 3, 2026, 4:03 p.m.