Triple
T7766004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbach |
E176146
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Hilden |
E103803
|
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: Hilden | Statement: [Rheinbach, hasTwinTown, Hilden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hilden Context triple: [Rheinbach, hasTwinTown, Hilden]
-
A.
Hilden
chosen
Hilden is a town in western Germany’s North Rhine-Westphalia region, known for its proximity to Düsseldorf and its mix of residential, commercial, and light industrial areas.
-
B.
Holten
Holten is a village in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
-
C.
Hanworth
Hanworth is a suburban residential area in west London, England, known for its parks, local amenities, and proximity to Heathrow Airport.
-
D.
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.
-
E.
Wallenhorst
Wallenhorst is a municipality in Lower Saxony, Germany, located near the city of Osnabrück.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7043279748190b30882e9cc6cca54 |
completed | March 27, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8c7e1a1408190a802d4f4afb8dd05 |
completed | March 29, 2026, 6:34 a.m. |
Created at: March 27, 2026, 4:09 p.m.