Triple
T17703650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Zierenberg |
E441373
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Zierenberg |
E441373
|
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: Zierenberg | Statement: [Battle of Zierenberg, location, Zierenberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zierenberg Context triple: [Battle of Zierenberg, location, Zierenberg]
-
A.
Zierenberg
chosen
Zierenberg is a small historic town in the German state of Hesse, notable for its medieval architecture and its role as the site of the Battle of Zierenberg.
-
B.
Ziegenberg
Ziegenberg is a locality in Hesse, Germany, historically notable for its role and nearby military installations during the later years of World War II.
-
C.
Hangelsberg
Hangelsberg is a village in the German state of Brandenburg, known as a district of the municipality Grünheide (Mark) in the Oder-Spree region.
-
D.
Aegidienberg
Aegidienberg is a district of the town of Bad Honnef in North Rhine-Westphalia, Germany, known for its scenic location in the Siebengebirge region.
-
E.
Memmingerberg
Memmingerberg is a small municipality in the Unterallgäu district of Bavaria in 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729528b88190bd8a104f6f6d4e69 |
completed | April 19, 2026, 6:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a02301ef8488190a71d06780a4f6b29 |
completed | May 11, 2026, 7:38 p.m. |
Created at: April 10, 2026, 10:05 a.m.