Triple
T16208475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eggishorn |
E393389
|
entity |
| Predicate | hasSummitStationElevation |
P102982
|
FINISHED |
| Object | around 2869 m |
—
|
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: around 2869 m | Statement: [Eggishorn, hasSummitStationElevation, around 2869 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitStationElevation Context triple: [Eggishorn, hasSummitStationElevation, around 2869 m]
-
A.
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).
-
B.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
C.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
D.
upperStationElevation
chosen
Indicates the elevation or height above a reference level (e.g., sea level) of the upper station in a system or structure.
-
E.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22710ef2c8190a8d7b9fb1666816c |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.