Triple
T6094817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Armoured Division (United Kingdom) |
E135850
|
entity |
| Predicate | garrison |
P75
|
FINISHED |
| Object | Hohne |
E466388
|
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: Hohne | Statement: [1st Armoured Division (United Kingdom), garrison, Hohne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hohne Context triple: [1st Armoured Division (United Kingdom), garrison, Hohne]
-
A.
Hohne
chosen
Hohne is a village in Lower Saxony, Germany, historically notable for its military garrison and association with British Army units.
-
B.
Hohberg
Hohberg is a municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
-
C.
Nyhausen
Nyhausen is a locality in Germany historically noted as the birthplace of the Swedish nobleman and soldier Philip Christoph von Königsmarck.
-
D.
Naunhof
Naunhof is a small town in the Free State of Saxony in eastern Germany, known for its surrounding lakes and forests near the city of Leipzig.
-
E.
Bernlohe
Bernlohe is a village-level district that forms part of the town of Roth in Bavaria, 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a963bac8190bc0c33fef187875c |
completed | March 22, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20d4e28b48190bb44675c5c035bd3 |
completed | March 24, 2026, 4:04 a.m. |
Created at: March 22, 2026, 4:12 p.m.