Triple
T6406624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regensburg |
E127596
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object |
Budenheim
Budenheim is a municipality in the German state of Rhineland-Palatinate, located near Mainz along the Rhine River.
|
E591029
|
NE FINISHED |
How this triple was built (4 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: Budenheim | Statement: [Regensburg, twinCity, Budenheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Budenheim Context triple: [Regensburg, twinCity, Budenheim]
-
A.
Insterburg
Insterburg was a historically significant town in former East Prussia, now known as Chernyakhovsk in Russia’s Kaliningrad Oblast.
-
B.
Olsberg
Olsberg is a small town in the Hochsauerland region of North Rhine-Westphalia, Germany, known for its scenic location in the Sauerland hills and outdoor recreation opportunities.
-
C.
Bromberg
Bromberg is the former German name for the city of Bydgoszcz, a major urban and industrial center in present-day north-central Poland.
-
D.
Neustadt
Neustadt is a district of the Austrian city of Salzburg, known for its central urban character within the historic and cultural landscape of the city.
-
E.
Neustadt
Neustadt is a vibrant district of Dresden, Germany, known for its historic architecture, lively arts scene, and numerous bars, cafes, and cultural venues.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Budenheim Triple: [Regensburg, twinCity, Budenheim]
Generated description
Budenheim is a municipality in the German state of Rhineland-Palatinate, located near Mainz along the Rhine River.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Budenheim Target entity description: Budenheim is a municipality in the German state of Rhineland-Palatinate, located near Mainz along the Rhine River.
-
A.
Insterburg
Insterburg was a historically significant town in former East Prussia, now known as Chernyakhovsk in Russia’s Kaliningrad Oblast.
-
B.
Olsberg
Olsberg is a small town in the Hochsauerland region of North Rhine-Westphalia, Germany, known for its scenic location in the Sauerland hills and outdoor recreation opportunities.
-
C.
Bromberg
Bromberg is the former German name for the city of Bydgoszcz, a major urban and industrial center in present-day north-central Poland.
-
D.
Neustadt
Neustadt is a district of the Austrian city of Salzburg, known for its central urban character within the historic and cultural landscape of the city.
-
E.
Neustadt
Neustadt is a vibrant district of Dresden, Germany, known for its historic architecture, lively arts scene, and numerous bars, cafes, and cultural venues.
- F. None of above. chosen
Provenance (5 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068b3541c8190be89b24b313d7300 |
completed | March 22, 2026, 10:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638af5450819089d0b68721eaea4d |
completed | March 27, 2026, 7:58 a.m. |
| NEDg | Description generation | batch_69c63b6213a881908c6c87c4672b8f3b |
completed | March 27, 2026, 8:10 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c63c5f7d508190bd263822cea1b782 |
completed | March 27, 2026, 8:14 a.m. |
Created at: March 22, 2026, 4:41 p.m.