Triple
T31010098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khumbu Valley |
E790185
|
entity |
| Predicate | highestPeakVisibleFrom |
P184865
|
FINISHED |
| Object | Mount Everest |
—
|
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: Mount Everest | Statement: [Khumbu Valley, highestPeakVisibleFrom, Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPeakVisibleFrom Context triple: [Khumbu Valley, highestPeakVisibleFrom, Mount Everest]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestPeakAccessible
Indicates that one location is the tallest peak that can be reached or accessed from another specified location or by a specified agent.
-
C.
highestPeaksLocatedIn
Indicates that the specified highest mountain peaks are geographically situated within the given location or region.
-
D.
peakOf
Indicates that one entity represents the highest or most extreme point, level, or intensity within the extent or progression of another entity.
-
E.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
- F. None of above. chosen
Provenance (4 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_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 29, 2026, 8:57 p.m.