Triple
T29296292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dingboche |
E742839
|
entity |
| Predicate | trekkingRegion |
P136500
|
FINISHED |
| Object | Everest Base Camp trekking route |
—
|
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 trekking route | Statement: [Dingboche, trekkingRegion, Everest Base Camp trekking route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekkingRegion Context triple: [Dingboche, trekkingRegion, Everest Base Camp trekking route]
-
A.
regionOfTour
Indicates that a specified geographic or administrative region is the location or scope within which a particular tour takes place.
-
B.
trekkingBase
Indicates a location that serves as the primary starting point or support hub for trekking activities.
-
C.
regionOfMountaineeringActivity
chosen
Indicates the geographic area where the mountaineering activity takes place or is carried out.
-
D.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
E.
skiRegion
Indicates that a location is recognized as a ski area or resort where skiing activities take place.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654459b481908684b3efa19d5bd5 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:06 p.m.