Triple
T10382046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Worringen |
E244664
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Worringen |
E844194
|
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: Worringen | Statement: [Battle of Worringen, location, Worringen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Worringen Context triple: [Battle of Worringen, location, Worringen]
-
A.
Worringen
chosen
Worringen is a district in the northern part of Cologne, Germany, historically notable as the site of the 1288 Battle of Worringen.
-
B.
Wehringen
Wehringen is a small municipality in Bavaria, Germany, situated in the region surrounding the city of Augsburg.
-
C.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
D.
Waldbröl
Waldbröl is a small town in North Rhine-Westphalia, Germany, known for its rural setting in the Bergisches Land region.
-
E.
Günsberg
Günsberg is a Swiss municipality located in the canton of Solothurn, known for its scenic setting near the Jura Mountains.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e992d8e08190aaa9a04925f52ccc |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9987838ac8190a6ba09305fc27621 |
completed | April 11, 2026, 12:40 a.m. |
Created at: April 6, 2026, 12:04 p.m.