Triple
T29127635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pangboche |
E738276
|
entity |
| Predicate | trekStageOnRouteTo |
P79762
|
FINISHED |
| Object | Everest Base Camp |
—
|
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 | Statement: [Pangboche, trekStageOnRouteTo, Everest Base Camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekStageOnRouteTo Context triple: [Pangboche, trekStageOnRouteTo, Everest Base Camp]
-
A.
trekStage
chosen
Indicates a specific segment or leg within a longer trek or journey, typically ordered as part of a multi-stage route.
-
B.
climbingRouteStage
Indicates a specific segment or phase within a larger climbing route, linking that portion to the overall route progression.
-
C.
trek
Indicates undertaking a long, often challenging journey, typically on foot, from one place to another.
-
D.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
E.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6622b76d481909dfcad6d272e74f0 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:29 a.m.