Triple
T12852239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak 7 |
E307351
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Peak 8 |
E308780
|
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: Peak 8 | Statement: [Peak 7, near, Peak 8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peak 8 Context triple: [Peak 7, near, Peak 8]
-
A.
Peak 8
chosen
Peak 8 is one of the main mountain areas at Breckenridge, featuring a central base village and a wide variety of ski terrain for all ability levels.
-
B.
Peak 6
Peak 6 is a high-alpine expansion area of Breckenridge known for its intermediate-to-advanced terrain and bowl skiing.
-
C.
Peak 7
Peak 7 is a popular intermediate-focused mountain area at Breckenridge Ski Resort in Colorado, known for its groomed blue runs and easy access via the BreckConnect Gondola.
-
D.
Peak 15
Peak 15 is an alternative historical name for Mount Everest, the world’s highest mountain above sea level in the Himalayas.
-
E.
North Peak
North Peak is one of the main summits of China’s Mount Hua, known for its dramatic cliffs and scenic mountain views.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97020eacc81909357b3398d17dc49 |
completed | April 10, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af511b4c8190bee09c938b2a7a12 |
completed | May 3, 2026, 2:13 a.m. |
Created at: April 9, 2026, 5:36 p.m.