Triple
T19357563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reinbek |
E484188
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Neuburg an der Donau |
—
|
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: Neuburg an der Donau | Statement: [Reinbek, twinTown, Neuburg an der Donau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neuburg an der Donau Context triple: [Reinbek, twinTown, Neuburg an der Donau]
-
A.
Neuburg an der Donau
chosen
Neuburg an der Donau is a historic Bavarian town on the Danube River in southern Germany, known for its Renaissance castle and former status as a ducal residence.
-
B.
Neuburg am Inn
Neuburg am Inn is a Bavarian municipality in southeastern Germany situated on the River Inn near the city of Passau.
-
C.
Wörth an der Donau
Wörth an der Donau is a small Bavarian town on the Danube River in southeastern Germany.
-
D.
Neuburg an der Kammel
Neuburg an der Kammel is a small municipality in the Bavarian region of Swabia in southern Germany.
-
E.
Neuötting
Neuötting is a small Bavarian town in southeastern Germany known for its historic town center and location near the Austrian border.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619096c1081909ce2cbf7ae804e73 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 10, 2026, 1:34 p.m.