Triple
T19438753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Peak |
E486295
|
entity |
| Predicate | summitDifficulty |
P135896
|
FINISHED |
| Object | non-technical in summer |
—
|
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: non-technical in summer | Statement: [Diamond Peak, summitDifficulty, non-technical in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitDifficulty Context triple: [Diamond Peak, summitDifficulty, non-technical in summer]
-
A.
typicalSummitTarget
Indicates that something is a usual or characteristic objective or destination associated with reaching a summit.
-
B.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
C.
summitAboveTreeline
Indicates that the summit of a landform is located above the natural treeline, where trees no longer grow due to environmental conditions.
-
D.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
E.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6336281b88190b1e5ad2606d7c314 |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.