Triple
T24197955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Foraker |
E599884
|
entity |
| Predicate | relativeLocationToPeak |
P44470
|
FINISHED |
| Object | southwest of Denali |
—
|
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: southwest of Denali | Statement: [Mount Foraker, relativeLocationToPeak, southwest of Denali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationToPeak Context triple: [Mount Foraker, relativeLocationToPeak, southwest of Denali]
-
A.
highestPeaksRelativeTo
Indicates a relationship where one location or region is associated with the tallest mountain peaks it contains, relative to surrounding areas or a defined reference set.
-
B.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
C.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
D.
areaPeakApprox
Indicates an approximate measurement or estimation of the peak area associated with an entity or event.
-
E.
highestNearbyPeakElevationInFeet
Indicates the elevation in feet of the tallest peak located within a defined nearby area of a given reference point.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.