Triple
T23975787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bond |
E604363
|
entity |
| Predicate | nearestNotablePeak |
P20909
|
FINISHED |
| Object | Bondcliff |
—
|
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: Bondcliff | Statement: [Mount Bond, nearestNotablePeak, Bondcliff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestNotablePeak Context triple: [Mount Bond, nearestNotablePeak, Bondcliff]
-
A.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
B.
notablePeak
chosen
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
C.
highestNearbyPeakElevationInFeet
Indicates the elevation in feet of the tallest peak located within a defined nearby area of a given reference point.
-
D.
nearestHigherPeak
Indicates that one peak is the closest peak that has a higher elevation than another specified peak.
-
E.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2ba11708190b8587bd006249ff5 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.