Triple
T26165227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Marshall |
E654230
|
entity |
| Predicate | rankingInAdirondackHighPeaksByElevation |
P103081
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [Mount Marshall, rankingInAdirondackHighPeaksByElevation, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingInAdirondackHighPeaksByElevation Context triple: [Mount Marshall, rankingInAdirondackHighPeaksByElevation, 25]
-
A.
AdirondackHighPeakRank
chosen
Indicates the ordinal ranking position of an Adirondack High Peak within the recognized list of such peaks.
-
B.
summitElevationRank
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
C.
rankingInNewYorkByElevation
Indicates the relative ordering of places located in New York based on their elevation above sea level.
-
D.
stateHighPointRank
Indicates the relative ranking position of a location as the highest point within a given state or comparable region.
-
E.
topographicProminenceRankInAlaska
Indicates the ranking position of a feature based on its topographic prominence relative to all other features in Alaska.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 8:32 p.m.