Triple
T25908725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Skylight |
E652829
|
entity |
| Predicate | rankByElevationInAdirondacks |
P103081
|
FINISHED |
| Object | one of the highest peaks |
—
|
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: one of the highest peaks | Statement: [Mount Skylight, rankByElevationInAdirondacks, one of the highest peaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByElevationInAdirondacks Context triple: [Mount Skylight, rankByElevationInAdirondacks, one of the highest peaks]
-
A.
AdirondackHighPeakRank
chosen
Indicates the ordinal ranking position of an Adirondack High Peak within the recognized list of such peaks.
-
B.
rankingInNewYorkByElevation
Indicates the relative ordering of places located in New York based on their elevation above sea level.
-
C.
summitElevationRank
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
D.
hasElevationRank
Indicates the relative ordering of an entity based on its elevation compared to others.
-
E.
stateHighPointRank
Indicates the relative ranking position of a location as the highest point within a given state or comparable region.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c2ece48190812532cb235714ad |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:28 a.m.