Triple
T33250625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agassiz Peak |
E851228
|
entity |
| Predicate | hasNearestHigherNeighbor |
P126574
|
FINISHED |
| Object | Humphreys Peak |
—
|
NE NERFINISHED |
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: Humphreys Peak | Statement: [Agassiz Peak, hasNearestHigherNeighbor, Humphreys Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearestHigherNeighbor Context triple: [Agassiz Peak, hasNearestHigherNeighbor, Humphreys Peak]
-
A.
hasNearbyPeak
Indicates that one location has another peak situated close to it in geographic space.
-
B.
hasHigherPeaksNearby
Indicates that an entity is located near other entities whose peak elevations are higher than its own.
-
C.
highestNearbyPoint
Indicates that one location is the highest point within a specified surrounding area relative to another location.
-
D.
hasNorthNeighbor
Indicates that one entity is located directly to the north of another entity.
-
E.
nearestHigherPeak
chosen
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:31 a.m.