Triple
T17921211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soest plain |
E448070
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Lippstadt |
—
|
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: Lippstadt | Statement: [Soest plain, contains, Lippstadt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lippstadt Context triple: [Soest plain, contains, Lippstadt]
-
A.
Lippstadt
chosen
Lippstadt is a historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
-
B.
Nordhorn
Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
-
C.
Remscheid
Remscheid is a city in North Rhine-Westphalia, Germany, known historically for its metalworking industry and as the birthplace of physicist Wilhelm Röntgen.
-
D.
Jülich
Jülich is a historic town in western Germany, known for its former status as a ducal residence and its significant Renaissance-era fortifications.
-
E.
Gardelegen
Gardelegen is a historic town in the German state of Saxony-Anhalt, known for its medieval architecture and its location in the Altmark region.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30a11748190be41361d108aee58 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 10:20 a.m.