Triple
T24019241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everest Base Camp (South) |
E594769
|
entity |
| Predicate | sideOfEverest |
P73665
|
FINISHED |
| Object | south side |
—
|
LITERAL FINISHED |
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: south side | Statement: [Everest Base Camp (South), sideOfEverest, south side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfEverest Context triple: [Everest Base Camp (South), sideOfEverest, south side]
-
A.
sideOfMountain
chosen
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
B.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
C.
includesHighestMountainOnEarth
Indicates that the subject entity contains or encompasses the location of the tallest mountain on Earth.
-
D.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
E.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or entity.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a7b5848190849e7a0f035465b3 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.