Triple
T10172335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baden District |
E235360
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Pottenstein |
E776153
|
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: Pottenstein | Statement: [Baden District, contains, Pottenstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pottenstein Context triple: [Baden District, contains, Pottenstein]
-
A.
Pottenstein
chosen
Pottenstein is a small town in Lower Austria known for its scenic surroundings and traditional Austrian character.
-
B.
Plöckenstein
Plöckenstein is a mountain on the border of Austria, Germany, and the Czech Republic, known as the highest peak of the Bohemian Forest.
-
C.
Goppenstein
Goppenstein is a small Swiss village in the canton of Valais, best known as a key railway junction and car shuttle station on the Lötschberg route through the Alps.
-
D.
Pennenfeld
Pennenfeld is a residential subdistrict of the Bonn borough of Bad Godesberg in 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9f6dd8819081588600499165ee |
completed | April 2, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d30101e3ec819095a587c0dae55f71 |
completed | April 6, 2026, 12:40 a.m. |
Created at: March 30, 2026, 9:10 p.m.