Triple
T18522725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildspitze |
E452629
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Weißkamm |
—
|
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: Weißkamm | Statement: [Wildspitze, locatedIn, Weißkamm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weißkamm Context triple: [Wildspitze, locatedIn, Weißkamm]
-
A.
Weißkamm
chosen
Weißkamm is a prominent subrange of the Ötztal Alps in Tyrol, Austria, known for its high glaciated peaks and alpine landscapes.
-
B.
Hochalmspitze
Hochalmspitze is a prominent mountain in the Austrian Alps, renowned for its glaciated summit and challenging alpine climbing routes.
-
C.
Lenzspitze
Lenzspitze is a prominent high-altitude peak in the Swiss Pennine Alps, known for its sharp ridges and challenging alpine climbing routes.
-
D.
Gerlachspitze
Gerlachspitze is the highest peak in the High Tatras and in Slovakia, renowned as a prominent alpine climbing and hiking destination in Central Europe.
-
E.
Wildspitze
Wildspitze is a prominent mountain in the Ötztal Alps of Tyrol, Austria, known as one of the country's highest and most popular alpine climbing peaks.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338f6da48190bdb374019d10db05 |
completed | April 19, 2026, 7:57 p.m. |
Created at: April 10, 2026, 11:37 a.m.