Triple

T14066587
Position Surface form Disambiguated ID Type / Status
Subject Gasherbrum I E338490 entity
Predicate alsoKnownAs P39 FINISHED
Object K5 E269866 NE 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: K5 | Statement: [Gasherbrum I, alsoKnownAs, K5]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: K5
Context triple: [Gasherbrum I, alsoKnownAs, K5]
  • A. K5 chosen
    K5 is an alternative name for Gasherbrum I, one of the world’s highest and most challenging eight-thousander peaks in the Karakoram range.
  • B. K5R4
    K5R4 is the ICAO airport code assigned to Foley Municipal Airport in Foley, Alabama, United States.
  • C. K 51
    K 51 was the military designation for the Junkers G 38, a large German four-engine transport aircraft of the interwar period later adapted for military use.
  • D. K6
    K6 is a prominent 7,000-meter-class mountain in Pakistan’s Karakoram range, known among high-altitude climbers for its challenging, relatively infrequently attempted routes.
  • E. K7
    K7 is a prominent and technically challenging high-altitude peak in Pakistan’s Karakoram range, renowned among mountaineers for its steep granite faces and remote location.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d81c67ba6c819091935650dfb3b895 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de568b81f08190a571004261c0e8e4 completed April 14, 2026, 3 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcb669111081909ccd167f41571a00 completed May 7, 2026, 3:57 p.m.
Created at: April 9, 2026, 10:21 p.m.