Triple
T11804439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mühlviertel |
E280708
|
entity |
| Predicate | highestPoint |
P210
|
FINISHED |
| Object | Plöckenstein |
E624512
|
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: Plöckenstein | Statement: [Mühlviertel, highestPoint, Plöckenstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plöckenstein Context triple: [Mühlviertel, highestPoint, Plöckenstein]
-
A.
Plöckenstein
chosen
Plöckenstein is a mountain on the border of Austria, Germany, and the Czech Republic, known as the highest peak of the Bohemian Forest.
-
B.
Pottenstein
Pottenstein is a small town in Lower Austria known for its scenic surroundings and traditional Austrian character.
-
C.
Ziegelstein
Ziegelstein is a district in Nuremberg, Germany, known for its residential character and proximity to Nuremberg Airport.
-
D.
Klötze
Klötze is a small town in the Altmark region of Saxony-Anhalt in central Germany.
-
E.
Philippstein
Philippstein is a small district or locality that forms part of the town of Braunfels in the German state of Hesse.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a5a2048190b68027f622366079 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1314300248190847b9c61bbfda121 |
completed | April 28, 2026, 10:14 p.m. |
Created at: April 8, 2026, 9:42 p.m.