Triple
T4629011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Ridge (Mount Elbert) |
E101167
|
entity |
| Predicate | summitReached |
P18072
|
FINISHED |
| Object | Mount Elbert summit |
—
|
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: Mount Elbert summit | Statement: [East Ridge (Mount Elbert), summitReached, Mount Elbert summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitReached Context triple: [East Ridge (Mount Elbert), summitReached, Mount Elbert summit]
-
A.
reachesSummit
chosen
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
B.
reachedSummitWith
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
hasSummitCross
Indicates that a mountain or peak is topped by a summit cross installed at or near its highest point.
-
E.
hasSummitMarker
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest point.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a300e6081909fa9f504aada33ea |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.