Triple
T12094732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiligenhaus |
E288041
|
entity |
| Predicate | district |
P2709
|
FINISHED |
| Object | Mettmann |
E842893
|
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: Mettmann | Statement: [Heiligenhaus, district, Mettmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mettmann Context triple: [Heiligenhaus, district, Mettmann]
-
A.
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.
-
B.
Meppen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
-
C.
Hennef
Hennef is a town in North Rhine-Westphalia, Germany, situated on the river Sieg near Bonn and known for its mix of residential areas, industry, and surrounding countryside.
-
D.
Euskirchen
Euskirchen is a town in the German state of North Rhine-Westphalia, known as a regional center near Bonn and the Eifel region.
-
E.
Mettmann district
chosen
Mettmann district is an administrative district in the German state of North Rhine-Westphalia, known for its mix of industrial towns and suburban communities near Düsseldorf.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91550ce508190babf5755e1553734 |
completed | April 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5e476d48190b6d9fafa7fe1cb9f |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 8, 2026, 9:48 p.m.