Triple
T31010106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khumbu Valley |
E790185
|
entity |
| Predicate | mainTrekRoute |
P152997
|
FINISHED |
| Object | Everest Base Camp trail |
—
|
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 trail | Statement: [Khumbu Valley, mainTrekRoute, Everest Base Camp trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTrekRoute Context triple: [Khumbu Valley, mainTrekRoute, Everest Base Camp trail]
-
A.
mainTour
Indicates that one entity serves as the primary or central tour associated with another entity.
-
B.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
C.
primaryRouteThrough
chosen
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
D.
firstMajorRoute
Indicates that the specified route is the primary or earliest major route associated with an entity (such as a location, project, or network).
-
E.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:57 p.m.