Triple
T7799574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridderkerk |
E180392
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Nordhorn |
E354605
|
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: Nordhorn | Statement: [Ridderkerk, hasTwinTown, Nordhorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nordhorn Context triple: [Ridderkerk, hasTwinTown, Nordhorn]
-
A.
Lippstadt
Lippstadt is a historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
-
B.
Meppen
chosen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
-
C.
Remscheid
Remscheid is a city in North Rhine-Westphalia, Germany, known historically for its metalworking industry and as the birthplace of physicist Wilhelm Röntgen.
-
D.
Wallenhorst
Wallenhorst is a municipality in Lower Saxony, Germany, located near the city of Osnabrück.
-
E.
Warendorf
Warendorf is a historic town in western Germany’s North Rhine-Westphalia, known for its well-preserved medieval old town and strong equestrian traditions.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cae985d8f08190b38d9d6848a7dc83 |
completed | March 30, 2026, 9:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05bd623b88190aeecaa70f92e5c3c |
completed | April 4, 2026, 12:31 a.m. |
Created at: March 30, 2026, 4:32 p.m.