Triple
T21314715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lützen (1632) |
E525434
|
entity |
| Predicate | associatedWithPlace |
P2830
|
FINISHED |
| Object | Lützen |
—
|
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: Lützen | Statement: [Battle of Lützen (1632), associatedWithPlace, Lützen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lützen Context triple: [Battle of Lützen (1632), associatedWithPlace, Lützen]
-
A.
Lützen
chosen
Lützen is a town in present-day Germany best known as the site of the 1632 Battle of Lützen during the Thirty Years' War, where Swedish King Gustavus Adolphus was killed.
-
B.
Altranstädt
Altranstädt is a village in Saxony, Germany, historically notable as the site of early 18th-century treaties during the Great Northern War.
-
C.
Bannewitz
Bannewitz is a municipality in the Free State of Saxony in eastern Germany, located just south of the city of Dresden.
-
D.
Schneidemühl
Schneidemühl was a former German town (now Piła in Poland) that historically served as an important regional administrative and railway center.
-
E.
Zeuthen
Zeuthen is a municipality in Brandenburg, Germany, known for hosting a major campus of the DESY particle physics research center.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dce6b4081909841ac0440fca5e4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 4:28 p.m.