Triple
T6551932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gronau (Westf) |
E151149
|
entity |
| Predicate | district |
P2709
|
FINISHED |
| Object | Borken |
E604598
|
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: Borken | Statement: [Gronau (Westf), district, Borken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borken Context triple: [Gronau (Westf), district, Borken]
-
A.
Borken
chosen
Borken is a town in western Germany that serves as an administrative and commercial center in the state of North Rhine-Westphalia.
-
B.
Hagen
Hagen is a city in the Ruhr region of North Rhine-Westphalia in western Germany, known historically as an industrial and transport hub.
-
C.
Hagen
Hagen is a surname of German origin borne by various notable individuals across fields such as music, sports, and academia.
-
D.
Insterburg
Insterburg was a historically significant town in former East Prussia, now known as Chernyakhovsk in Russia’s Kaliningrad Oblast.
-
E.
Winsum
Winsum is a historic village and former municipality in the Dutch province of Groningen, known for its old churches, windmills, and picturesque canals.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ae05cd988190a013226b14cd98f0 |
completed | March 27, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6eed5afb88190aa4fdae9cda04c54 |
completed | March 27, 2026, 8:55 p.m. |
Created at: March 27, 2026, 1:51 p.m.