Triple
T28483224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khumbu Pasang Lhamu Rural Municipality |
E720749
|
entity |
| Predicate | majorTrekkingRoute |
P101130
|
FINISHED |
| Object | Everest Base Camp trek |
—
|
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: Everest Base Camp trek | Statement: [Khumbu Pasang Lhamu Rural Municipality, majorTrekkingRoute, Everest Base Camp trek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTrekkingRoute Context triple: [Khumbu Pasang Lhamu Rural Municipality, majorTrekkingRoute, Everest Base Camp trek]
-
A.
glacialRoute
Indicates a path or course shaped, carved, or followed by a glacier as it moves across a landscape.
-
B.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
C.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
-
D.
isMajorTourismRoute
chosen
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
E.
includesMountainRoutes
Indicates that the described route, path, or itinerary contains one or more segments that pass through or over mountainous terrain.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 28, 2026, 2:56 a.m.