Triple
T12160645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Pszczyna |
E289695
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Pszczyna |
E843820
|
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: Pszczyna | Statement: [Battle of Pszczyna, location, Pszczyna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pszczyna Context triple: [Battle of Pszczyna, location, Pszczyna]
-
A.
Pszczyna
chosen
Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque old town.
-
B.
Ojców
Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
-
C.
Zbrzyca
Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
-
D.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
-
E.
Skrzyczne
Skrzyczne is a prominent mountain in southern Poland known for its hiking trails, ski resort, and panoramic views over the Silesian Beskids.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c395e48190a16e97fd29787a51 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ec19c508190912c3fe186f8a992 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 8, 2026, 9:50 p.m.