Triple

T33058293
Position Surface form Disambiguated ID Type / Status
Subject Ngadi Chuli E845901 entity
Predicate approachTrekVia P118683 FINISHED
Object Annapurna Circuit / Manaslu region trails 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: Annapurna Circuit / Manaslu region trails | Statement: [Ngadi Chuli, approachTrekVia, Annapurna Circuit / Manaslu region trails]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approachTrekVia
Context triple: [Ngadi Chuli, approachTrekVia, Annapurna Circuit / Manaslu region trails]
  • A. approachRoute
    Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
  • B. trekkingBase
    Indicates a location that serves as the primary starting point or support hub for trekking activities.
  • C. trailAccess
    Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
  • D. trailblazerFor
    Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
  • E. hasApproachTrail chosen
    Indicates that there is a designated trail or path providing access or approach to a particular location or feature.
  • 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_69f3495333b8819095e9af56855b9061 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fecd0a732c819097bdd3eb69b6158c completed May 9, 2026, 5:58 a.m.
PD Predicate disambiguation batch_69fecc0318d481908b5b20598a76a9fe completed May 9, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:25 a.m.