Triple
T35950628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suru Valley |
E1039711
|
entity |
| Predicate | notablePeakView |
P20909
|
FINISHED |
| Object | Nun Kun massif |
E1638346
|
NE 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: Nun Kun massif | Statement: [Suru Valley, notablePeakView, Nun Kun massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeakView Context triple: [Suru Valley, notablePeakView, Nun Kun massif]
-
A.
notablePeak
chosen
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
B.
notablePeakSpecialization
Indicates that an entity’s most prominent or distinguishing peak, high point, or summit is characterized by a specific type, category, or specialization.
-
C.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
D.
depictsPeak
Indicates that one entity visually represents or portrays the highest or most intense point of another entity or process.
-
E.
notableSubpeak
Indicates that one peak is a significant or noteworthy subsidiary summit of another, higher or primary peak.
- F. None of above.
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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6ff63c48190baa1803c2bce5fa7 |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.