Triple
T12731512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mikołów |
E304247
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Mikołów |
E842910
|
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: Mikołów | Statement: [Battle of Mikołów, location, Mikołów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikołów Context triple: [Battle of Mikołów, location, Mikołów]
-
A.
Mikołów
chosen
Mikołów is a historic town in southern Poland known for its traditional Silesian character and proximity to the regional capital, Katowice.
-
B.
Miłków
Miłków is a village in southwestern Poland situated in the scenic Jelenia Góra Valley near the Karkonosze Mountains.
-
C.
Sułów
Sułów is a village in eastern Poland located within Zamość County in the Lublin Voivodeship.
-
D.
Pszczyna
Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque old town.
-
E.
Kromołów
Kromołów is a historic district of the city of Zawiercie in southern Poland, known as the place where the Warta River begins.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96467a2248190aff1ebb5db84b3c6 |
completed | April 10, 2026, 8:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002d92c9788190aa4523a1e47bc561 |
completed | May 10, 2026, 7:02 a.m. |
Created at: April 9, 2026, 5:25 p.m.