Triple
T6836031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alstätte |
E157451
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | Stadt Ahaus |
E691013
|
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: Stadt Ahaus | Statement: [Alstätte, governedBy, Stadt Ahaus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stadt Ahaus Context triple: [Alstätte, governedBy, Stadt Ahaus]
-
A.
Stadt Ahaus
chosen
Stadt Ahaus is a town in the district of Borken in North Rhine-Westphalia, Germany, known for its historic castle and proximity to the Dutch border.
-
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.
Bentheim
Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
-
D.
Lippstadt
Lippstadt is a historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
-
E.
Iserlohn
Iserlohn is a city in the Märkischer Kreis district of North Rhine-Westphalia, Germany, known historically for its role in World War II and its metalworking and industrial heritage.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67c1c508190ab39b8aaaaacc628 |
completed | March 27, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9cf41d5308190be3ce32a4f7b707a |
completed | March 30, 2026, 1:17 a.m. |
Created at: March 27, 2026, 2:19 p.m.