Triple
T23428687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rax Alps |
E563263
|
entity |
| Predicate | highestPoint |
P210
|
FINISHED |
| Object | Heukuppe |
—
|
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: Heukuppe | Statement: [Rax Alps, highestPoint, Heukuppe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heukuppe Context triple: [Rax Alps, highestPoint, Heukuppe]
-
A.
Heukuppe
chosen
Heukuppe is a prominent mountain peak in the Eastern Alps, known as the highest summit of the Rax plateau on the border of Lower Austria and Styria.
-
B.
Havelterberg
Havelterberg is a modest hill and natural area in the Dutch province of Drenthe, known for its scenic landscapes and prehistoric burial mounds.
-
C.
Hesselberg
Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
-
D.
Humberg hill
Humberg hill is a wooded elevation near Kaiserslautern, Germany, known as a local recreation area crowned by the historic Humberg Tower.
-
E.
Ochsenkopf
Ochsenkopf is one of the highest and most prominent mountains in Germany’s Fichtelgebirge, known for its ski area, hiking trails, and summit broadcasting tower.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ba29881909945690496f28d65 |
completed | April 29, 2026, 6:29 a.m. |
Created at: April 17, 2026, 5:48 p.m.