Triple
T17515665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergamasque Alps and Prealps |
E426560
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Pizzo Coca |
—
|
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: Pizzo Coca | Statement: [Bergamasque Alps and Prealps, hasPeak, Pizzo Coca]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pizzo Coca Context triple: [Bergamasque Alps and Prealps, hasPeak, Pizzo Coca]
-
A.
Pizzo Coca
chosen
Pizzo Coca is a prominent mountain peak in northern Italy, known as the highest summit in the Bergamo Alps and a popular destination for experienced hikers and climbers.
-
B.
Piz d’Err
Piz d’Err is a mountain peak in the Albula Alps of eastern Switzerland, known for its rugged terrain and scenic alpine surroundings.
-
C.
Pizzo Centrale
Pizzo Centrale is a prominent mountain peak in the Swiss Alps known for its central position and panoramic views within the Lepontine range.
-
D.
Piz Boè
Piz Boè is a prominent mountain peak in the Dolomites of northern Italy, popular with hikers and climbers for its panoramic alpine views.
-
E.
Pizzo Rotondo
Pizzo Rotondo is a prominent mountain peak in the Swiss Alps known for its elevation and panoramic alpine views.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4526097388190ba1a949064962a24 |
completed | April 19, 2026, 3:56 a.m. |
Created at: April 10, 2026, 5:49 a.m.