Triple
T17827671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Plata Peak |
E445161
|
entity |
| Predicate | parentPeak |
P1319
|
FINISHED |
| Object | Mount Elbert |
—
|
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 Elbert | Statement: [La Plata Peak, parentPeak, Mount Elbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mount Elbert Context triple: [La Plata Peak, parentPeak, Mount Elbert]
-
A.
Mount Elbert
chosen
Mount Elbert is the highest peak in the Rocky Mountains and the tallest mountain in Colorado, located in the Sawatch Range.
-
B.
Uncompahgre Peak
Uncompahgre Peak is a prominent fourteener in southwestern Colorado, known for its broad summit and status as the highest point in the San Juan Mountains.
-
C.
Elbert
Elbert is a masculine given name of English origin, historically borne by figures such as American lawyer and steel industry executive Elbert H. Gary.
-
D.
Apache Peak
Apache Peak is a prominent high-elevation summit in Colorado’s Front Range, known for its rugged alpine terrain within the Indian Peaks Wilderness.
-
E.
Longs Peak
Longs Peak is a prominent fourteener in Colorado’s Front Range, renowned for its dramatic profile and challenging Keyhole Route climb.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48915d0fc819080ab03feb2465834 |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.