Triple
T6206781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotherham |
E138767
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Riesa |
E380063
|
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: Riesa | Statement: [Rotherham, hasTwinTown, Riesa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riesa Context triple: [Rotherham, hasTwinTown, Riesa]
-
A.
Riesa
chosen
Riesa is a town in the German state of Saxony, situated on the Elbe River and known historically as an important regional railway and industrial center.
-
B.
Bischofswerda
Bischofswerda is a small town in the Saxony region of eastern Germany, known as a local commercial and transport hub near the city of Dresden.
-
C.
Bautzen
Bautzen is a historic town in eastern Germany known for its well-preserved medieval architecture and as a cultural center of the Sorbian minority.
-
D.
Neukieritzsch
Neukieritzsch is a small municipality in the German state of Saxony, situated south of Leipzig and known historically as a local railway junction.
-
E.
Zinnowitz
Zinnowitz is a seaside resort town on Germany’s Baltic Sea coast, known for its sandy beaches, historic spa architecture, and tourism on the island of Usedom.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06270b8d08190a81bc03c8175b989 |
completed | March 22, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e3dd76508190aba82a4a74c74bea |
completed | March 27, 2026, 1:56 a.m. |
Created at: March 22, 2026, 4:20 p.m.