Triple
T5809319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kliszów |
E128826
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Kliszów |
E211075
|
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: Kliszów | Statement: [Battle of Kliszów, location, Kliszów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kliszów Context triple: [Battle of Kliszów, location, Kliszów]
-
A.
Krzeszowice
Krzeszowice is a town in southern Poland known for its historic spa traditions and picturesque location near Kraków.
-
B.
Kozłowo
Kozłowo is a village in northern Poland that serves as an important local center within the Warmian-Masurian Voivodeship.
-
C.
Sułoszowa
Sułoszowa is a village in southern Poland known for its unusually long, single-street layout and traditional rural character.
-
D.
Człuchów
Człuchów is a historic town in northern Poland known for its medieval Teutonic castle ruins and surrounding lakes.
-
E.
Staszów
chosen
Staszów is a historic town in south-central Poland known for its medieval origins and location within the Świętokrzyskie region.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1867a481909a7ea3331dbb04ce |
completed | March 22, 2026, 5:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c098416504819089356b68fabdf737 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:52 p.m.