Triple
T20369463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleiloch Dam |
E497009
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Saalburg-Ebersdorf |
—
|
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: Saalburg-Ebersdorf | Statement: [Bleiloch Dam, locatedNear, Saalburg-Ebersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saalburg-Ebersdorf Context triple: [Bleiloch Dam, locatedNear, Saalburg-Ebersdorf]
-
A.
Ebersdorf
chosen
Ebersdorf is a historic town in present-day Germany that once served as the capital of one of the small Reuss principalities.
-
B.
Erbach-Schönberg
Erbach-Schönberg was a mediatized German noble line and territory associated with the House of Erbach in the historic region of Hesse.
-
C.
Eberhardzell
Eberhardzell is a rural municipality in the district of Biberach in the German state of Baden-Württemberg.
-
D.
Reuss-Ebersdorf
Reuss-Ebersdorf was a small historical German principality ruled by a branch of the House of Reuss within the Holy Roman Empire and its successor states.
-
E.
Baldramsdorf
Baldramsdorf is a municipality in the Austrian state of Carinthia, known for its Alpine setting near the town of Spittal an der Drau.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6787454a88190ae87d9b3c9b5ad27 |
completed | April 20, 2026, 7:03 p.m. |
Created at: April 16, 2026, 11:26 a.m.