Triple
T23285207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roer Department |
E588966
|
entity |
| Predicate | containsPresentDayCity |
P58091
|
FINISHED |
| Object | Eschweiler |
—
|
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: Eschweiler | Statement: [Roer Department, containsPresentDayCity, Eschweiler]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eschweiler Context triple: [Roer Department, containsPresentDayCity, Eschweiler]
-
A.
Eschweiler
chosen
Eschweiler is a town in western Germany near Aachen, known for its industrial history and location in the state of North Rhine-Westphalia.
-
B.
Wiehl
Wiehl is a small town in western Germany’s North Rhine-Westphalia region, known for its picturesque setting in the hilly Bergisches Land and its mix of rural charm and light industry.
-
C.
Wiehl
Wiehl is a river in North Rhine-Westphalia, Germany, that flows through the Bergisches Land region before joining the Agger.
-
D.
Odenkirchen
Odenkirchen is a district in the city of Mönchengladbach in western Germany, historically a small town in North Rhine-Westphalia.
-
E.
Hörschweiler
Hörschweiler is a village-level subdivision of the town of Altensteig in the state of Baden-Württemberg, Germany.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1964600888190b40ecbefdc8aec64 |
completed | April 29, 2026, 5:25 a.m. |
Created at: April 17, 2026, 4:59 p.m.