Triple

T7834307
Position Surface form Disambiguated ID Type / Status
Subject Eight-thousander E181651 entity
Predicate notableChallenge P49070 FINISHED
Object climbing all 14 eight-thousanders 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: climbing all 14 eight-thousanders | Statement: [Eight-thousander, notableChallenge, climbing all 14 eight-thousanders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableChallenge
Context triple: [Eight-thousander, notableChallenge, climbing all 14 eight-thousanders]
  • A. challengeUndertaken
    Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
  • B. notableObjective chosen
    Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
  • C. challengeType
    Indicates the specific category or kind of challenge associated with an action or relationship between entities.
  • D. notableStruggles
    Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
  • E. challenger
    Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
  • 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_69ca8284a25c8190a1a20afad30da792 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb064a47648190af2ca2b336584a92 completed March 30, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69cae91e98988190abd4ece75932c589 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:45 p.m.