Triple
T15875254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balsam Cap |
E384937
|
entity |
| Predicate | prominenceFt |
P10298
|
FINISHED |
| Object | 403 |
—
|
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: 403 | Statement: [Balsam Cap, prominenceFt, 403]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominenceFt Context triple: [Balsam Cap, prominenceFt, 403]
-
A.
prominenceFeature
Indicates that one entity serves as a notable or distinguishing feature that contributes significantly to the prominence or recognizability of another entity.
-
B.
prominenceType
Indicates the specific kind or category of prominence or notability associated with an entity in a given context.
-
C.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
D.
topographicProminence
chosen
Indicates the height of a peak’s summit relative to the lowest contour line encircling it and no higher summit, expressing how much it stands out from surrounding terrain.
-
E.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.