Triple
T34080685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuptse I |
E874031
|
entity |
| Predicate | highestSubpeakOf |
P193076
|
FINISHED |
| Object | Nuptse massif |
—
|
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: Nuptse massif | Statement: [Nuptse I, highestSubpeakOf, Nuptse massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestSubpeakOf Context triple: [Nuptse I, highestSubpeakOf, Nuptse massif]
-
A.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
B.
highestPeaksRelativeTo
Indicates a relationship where one location or region is associated with the tallest mountain peaks it contains, relative to surrounding areas or a defined reference set.
-
C.
highestSurroundingPeaks
Indicates that certain peaks are the tallest among all peaks in the surrounding area of a given location or peak.
-
D.
subpeakElevation
Indicates the elevation value associated with a subpeak relative to a main peak or surrounding terrain.
-
E.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 1:52 a.m.