Triple

T13362874
Position Surface form Disambiguated ID Type / Status
Subject Nelion E318861 entity
Predicate climbingRequires P97397 FINISHED
Object route-finding skills 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: route-finding skills | Statement: [Nelion, climbingRequires, route-finding skills]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: climbingRequires
Context triple: [Nelion, climbingRequires, route-finding skills]
  • A. requiresTechnicalClimbing chosen
    Indicates that performing or traversing the subject (e.g., a route, path, or feature) necessitates the use of technical climbing skills, techniques, and/or specialized equipment.
  • B. climbingUse
    Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
  • C. canClimb
    Indicates that one entity has the ability or permission to climb another entity or surface.
  • D. climbingAccess
    Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
  • E. climbingActivity
    Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
  • 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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69da628affd081909f1790d333f0eef4 completed April 11, 2026, 3:02 p.m.
PD Predicate disambiguation batch_69d9a02c9abc8190b328e7bae747bfc5 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:32 p.m.