Triple
T12873744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulder Mountains (Idaho) |
E307911
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ryan Peak |
E1242861
|
NE 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: Ryan Peak | Statement: [Boulder Mountains (Idaho), contains, Ryan Peak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ryan Peak Context triple: [Boulder Mountains (Idaho), contains, Ryan Peak]
-
A.
Ryan Peak
chosen
Ryan Peak is a prominent mountain summit in central Idaho known for being the tallest point in the Boulder Mountains range.
-
B.
Wilson Peak
Wilson Peak is a prominent and rugged fourteener in southwestern Colorado, famed for its striking pyramid shape and frequent appearance in outdoor imagery and branding.
-
C.
Notch Peak
Notch Peak is a dramatic limestone mountain in western Utah known for its sheer cliffs and prominence in the House Range.
-
D.
Noe Peak
Noe Peak is one of the two summits that form the iconic Twin Peaks hills overlooking San Francisco, California.
-
E.
Keynot Peak
Keynot Peak is a prominent mountain summit in eastern California known for being the loftiest point in the remote and rugged Inyo Mountains range.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d970f87aa48190a7234424a6badef0 |
completed | April 10, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dbf2567c81909ab6054ade27afac |
completed | May 10, 2026, 7:26 p.m. |
Created at: April 9, 2026, 5:38 p.m.