Triple
T12566851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Westphalia |
E295497
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Quakenbrück |
E14423
|
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: Quakenbrück | Statement: [Province of Westphalia, containsSettlement, Quakenbrück]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Quakenbrück Context triple: [Province of Westphalia, containsSettlement, Quakenbrück]
-
A.
Quakenbrück
chosen
Quakenbrück is a small historic town in Lower Saxony, Germany, known for its medieval architecture and location in the Artland region.
-
B.
Kleeberg
Kleeberg is a Polish surname most notably associated with General Franciszek Kleeberg, a commander in the early stages of World War II.
-
C.
Warthbrücken
Warthbrücken is the German name for the Polish town of Koło, located in central Poland on the Warta River.
-
D.
Bersenbrück
Bersenbrück is a small town in Lower Saxony, Germany, known for its historic abbey and its location on the river Hase.
-
E.
Hochbrück
Hochbrück is a district of the Bavarian town of Garching near Munich, known for its industrial areas and proximity to major research and technology facilities.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954a325948190994bcfc9d571a3a8 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f655914f908190afbebbec3cb57e73 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 11:49 p.m.