Triple
T30759904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sanford South Peak |
E783203
|
entity |
| Predicate | subpeakOf |
P1319
|
FINISHED |
| Object | Mount Sanford |
—
|
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: Mount Sanford | Statement: [Mount Sanford South Peak, subpeakOf, Mount Sanford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subpeakOf Context triple: [Mount Sanford South Peak, subpeakOf, Mount Sanford]
-
A.
notableSubpeak
Indicates that one peak is a significant or noteworthy subsidiary summit of another, higher or primary peak.
-
B.
parentPeak
chosen
Indicates that one peak is the higher or primary peak to which another, subordinate peak is topographically related.
-
C.
isMajorPeakOf
Indicates that one peak is a primary or most prominent summit within a specified mountain, range, or geographic area.
-
D.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
E.
centralPeak
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f9b56988190a95f2706bb6b3217 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.