Triple
T14310360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verwood |
E354810
|
entity |
| Predicate | hasTwinning |
P919
|
FINISHED |
| Object | Liederbach am Taunus |
E811116
|
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: Liederbach am Taunus | Statement: [Verwood, hasTwinning, Liederbach am Taunus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liederbach am Taunus Context triple: [Verwood, hasTwinning, Liederbach am Taunus]
-
A.
Lüßbach
Lüßbach is a small river in Bavaria, Germany, that serves as one of the tributaries feeding into Lake Starnberg.
-
B.
Oberharmersbach
Oberharmersbach is a small municipality in southwestern Germany’s Black Forest region, known for its rural landscape and traditional Baden culture.
-
C.
Riedbach
Riedbach is a small municipality in the Bavarian region of Franconia in Germany.
-
D.
Lorsbach
chosen
Lorsbach is a district of the town Hofheim am Taunus in the German state of Hesse, situated in the Taunus mountain region.
-
E.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b26da48190a96e2f60ace51335 |
completed | April 14, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d3124488190b2ea35949294e297 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:12 a.m.