Triple
T4527394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassin's Ridge |
E106211
|
entity |
| Predicate | onSummit |
P8024
|
FINISHED |
| Object | Denali summit plateau |
—
|
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: Denali summit plateau | Statement: [Cassin's Ridge, onSummit, Denali summit plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onSummit Context triple: [Cassin's Ridge, onSummit, Denali summit plateau]
-
A.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
B.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
C.
hasSummit
chosen
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
reachedSummitWith
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
E.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd577737848190ad509c8bb8e57ec0 |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.