Triple
T18321120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Minden |
E438880
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Minden-Ravensberg |
E387272
|
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: Minden-Ravensberg | Statement: [Principality of Minden, successor, Minden-Ravensberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Minden-Ravensberg Context triple: [Principality of Minden, successor, Minden-Ravensberg]
-
A.
Minden-Ravensberg region
chosen
The Minden-Ravensberg region is a historical area in present-day North Rhine-Westphalia, Germany, known for its role in Prussian administrative history and its distinctive cultural and religious traditions.
-
B.
Minschter
Minschter is the Alsatian name for the city of Munster in the Alsace region of France.
-
C.
Ravensberg
Ravensberg was a historical county in northwestern Germany that became part of the expanding territorial holdings of Brandenburg-Prussia.
-
D.
Mundenheim
Mundenheim is a district of the industrial city of Ludwigshafen am Rhein in the German state of Rhineland-Palatinate.
-
E.
Lenzinghausen
Lenzinghausen is a district or locality within the town of Spenge in the German state of North Rhine-Westphalia.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a03c4c8224c819085369e23b7265dcb |
completed | May 13, 2026, 12:24 a.m. |
Created at: April 10, 2026, 10:36 a.m.