Triple
T4252055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lippstadt |
E95876
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Lippstadt |
E567830
|
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: Lippstadt | Statement: [Battle of Lippstadt, namedAfter, Lippstadt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lippstadt Context triple: [Battle of Lippstadt, namedAfter, 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.
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.
-
C.
Detmold
Detmold is a historic town in northwestern Germany that served as the capital and residence city of the former Principality of Lippe.
-
D.
Recklinghausen
Recklinghausen is a city in the Ruhr area of North Rhine-Westphalia, western Germany, known historically for coal mining and its role as a regional administrative center.
-
E.
Meppen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ebc98e08190915ac309a51ef87f |
completed | March 12, 2026, 11:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1351018b48190910c3dad6c0f9850 |
completed | March 23, 2026, 12:41 p.m. |
Created at: March 12, 2026, 11:06 p.m.