Triple
T12337790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarrebourg |
E294134
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Radeberg |
E638756
|
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: Radeberg | Statement: [Sarrebourg, hasTwinTown, Radeberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Radeberg Context triple: [Sarrebourg, hasTwinTown, Radeberg]
-
A.
Radeberg
chosen
Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
-
B.
Tureberg
Tureberg is a central district in Sollentuna Municipality, Sweden, known for housing the municipal center and key public services.
-
C.
Treuenbrietzen
Treuenbrietzen is a historic town in the German state of Brandenburg, known for its medieval architecture and role in Reformation-era history.
-
D.
Löbau
Löbau is a small town in the Free State of Saxony in eastern Germany, known for its historic architecture and location in the Lusatian Highlands.
-
E.
Wuhletal
Wuhletal is a valley landscape in Berlin shaped by the course of the Wuhle river, featuring green spaces, walking paths, and recreational areas.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f678698819091462b44ff3435f6 |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6555e525c8190aa72da362fae1e3e |
completed | May 2, 2026, 7:49 p.m. |
Created at: April 8, 2026, 9:53 p.m.