Triple
T19309101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Succession of Landshut |
E482918
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Landshut |
—
|
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: Landshut | Statement: [War of the Succession of Landshut, location, Landshut]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Landshut Context triple: [War of the Succession of Landshut, location, Landshut]
-
A.
Landshut
chosen
Landshut is a historic Bavarian city in southeastern Germany known for its well-preserved medieval architecture and the landmark Trausnitz Castle.
-
B.
Augsburg
Augsburg is one of Germany’s oldest cities, a historic Bavarian center known for its rich Renaissance heritage and role as a major medieval trading hub.
-
C.
Kempten
Kempten is a historic town in Bavaria, Germany, considered one of the country’s oldest urban settlements and known for its location in the Allgäu region.
-
D.
Kaufbeuren
Kaufbeuren is a historic Bavarian town in southern Germany known for its well-preserved medieval old town and traditional Swabian culture.
-
E.
Altdorf (Landshut)
Altdorf (Landshut) is a municipality in Lower Bavaria, Germany, situated near the city of Landshut.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cc62e08190b5ba5dfc44efdc5c |
completed | April 20, 2026, 10:49 a.m. |
Created at: April 10, 2026, 1:32 p.m.