Triple
T25322380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper Spur |
E634917
|
entity |
| Predicate | hasSummitElevationApprox |
P165303
|
FINISHED |
| Object | about 10,500 feet |
—
|
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: about 10,500 feet | Statement: [Cooper Spur, hasSummitElevationApprox, about 10,500 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitElevationApprox Context triple: [Cooper Spur, hasSummitElevationApprox, about 10,500 feet]
-
A.
hasSummitAbove
Indicates that one summit is located at a higher elevation than another summit.
-
B.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s summit.
-
C.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
D.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
E.
hasSummitFacility
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or peak).
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 21, 2026, 1:29 p.m.