Triple
T16850504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lutterberg |
E409660
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Lutterberg |
E409660
|
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: Lutterberg | Statement: [Battle of Lutterberg, locatedIn, Lutterberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lutterberg Context triple: [Battle of Lutterberg, locatedIn, Lutterberg]
-
A.
Lutterberg
chosen
Lutterberg is a village in Lower Saxony, Germany, historically notable as the site of the 1758 Battle of Lutterberg during the Seven Years' War.
-
B.
Hesselberg
Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
-
C.
Widdersberg
Widdersberg is a small village that forms one of the local subdivisions of the municipality of Münsing in Bavaria, Germany.
-
D.
Hermannstein
Hermannstein is a district of the German city of Wetzlar in the state of Hesse.
-
E.
Landensberg
Landensberg is a small municipality in the Bavarian region of southern Germany.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b378dda48190ab81d75f2cfe3ab3 |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dbfb781881908f4d56f523e78f7a |
completed | May 10, 2026, 7:26 p.m. |
Created at: April 10, 2026, 5:24 a.m.