Triple
T17177521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todtnau |
E416898
|
entity |
| Predicate | nearbyMountain |
P10602
|
FINISHED |
| Object | Feldberg |
E89914
|
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: Feldberg | Statement: [Todtnau, nearbyMountain, Feldberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feldberg Context triple: [Todtnau, nearbyMountain, Feldberg]
-
A.
Feldberg
chosen
Feldberg is the tallest mountain in Germany’s Black Forest region, known for its scenic landscapes and popular hiking and skiing opportunities.
-
B.
Feldberg
Feldberg is a small town in northeastern Germany known for its scenic lakes and forests within the Mecklenburg Lake District.
-
C.
Kohnstein
Kohnstein is a hill in Thuringia, Germany, whose tunnels were used by the Nazis during World War II to house the Mittelwerk underground factory for V-2 rocket production.
-
D.
Eibenberg
Eibenberg is a small locality that forms one of the subdivisions of the municipality of Burkhardtsdorf in Saxony, Germany.
-
E.
Felsberg
Felsberg is a settlement located in the historical region of Westphalia in western Germany.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ee5008190a73875b39841fd9f |
completed | April 18, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a016747a8908190a7ce1408abc70c47 |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:37 a.m.