Triple
T17080322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenmile Range |
E414452
|
entity |
| Predicate | hasSummitOver |
P8024
|
FINISHED |
| Object | 14000 ft |
—
|
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: 14000 ft | Statement: [Tenmile Range, hasSummitOver, 14000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitOver Context triple: [Tenmile Range, hasSummitOver, 14000 ft]
-
A.
hasSummitFinish
Indicates that an event or stage concludes at or near the summit of a climb or peak.
-
B.
hasSummit
chosen
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
C.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
D.
hasSummitConditions
Indicates that specific environmental or situational conditions required for a summit (e.g., peak ascent or high-level meeting) are present or satisfied.
-
E.
hasSummitCross
Indicates that a mountain or peak is topped by a summit cross installed at or near 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe24a6481908b4596c95220df4a |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.