Triple
T609731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnhem |
E12070
|
entity |
| Predicate | twinnedWith |
P1072
|
FINISHED |
| Object | Gera |
E22181
|
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: Gera | Statement: [Arnhem, twinnedWith, Gera]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gera Context triple: [Arnhem, twinnedWith, Gera]
-
A.
Gera
chosen
Gera is a city in the German state of Thuringia, known for its industrial heritage and historic architecture along the White Elster river.
-
B.
Lahn
The Lahn is a river in western Germany that flows through the states of North Rhine-Westphalia, Hesse, and Rhineland-Palatinate before joining the Rhine.
-
C.
Pirna
Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
-
D.
Vogtland
Vogtland is a hilly, historically rich region in central Europe spanning parts of Saxony, Thuringia, Bavaria, and the Czech Republic, known for its musical instrument making and scenic landscapes.
-
E.
Ruhr
The Ruhr is a river in western Germany that flows through the Ruhr industrial region before joining the Rhine.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df68f2c8190a0ee9da4692b2a62 |
completed | March 1, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a6732a8c0881909753261f9256fcf2 |
completed | March 3, 2026, 5:35 a.m. |
Created at: March 1, 2026, 7:35 p.m.