Triple
T23458759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brühl, Germany |
E568006
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Schwetzingen |
—
|
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: Schwetzingen | Statement: [Brühl, Germany, twinTown, Schwetzingen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwetzingen Context triple: [Brühl, Germany, twinTown, Schwetzingen]
-
A.
Schwetzingen
chosen
Schwetzingen is a town in southwestern Germany renowned for its Baroque palace and extensive formal gardens.
-
B.
Königsbrunn
Königsbrunn is a town in Bavaria, Germany, located just south of Augsburg and known as a residential and commercial suburb of the city.
-
C.
Wolfenweiler
Wolfenweiler is a village in southwestern Germany, known historically as the birthplace of cartographer Martin Waldseemüller.
-
D.
Schwabmünchen
Schwabmünchen is a small Bavarian town in southern Germany known for its historic center and location near the city of Augsburg.
-
E.
Notzingen
Notzingen is a small municipality in the German state of Baden-Württemberg, located in the Stuttgart region.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a699c0088190a84d7a495a3e3d61 |
completed | April 29, 2026, 6:35 a.m. |
Created at: April 17, 2026, 5:53 p.m.