Triple
T12977025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skawinka River |
E321550
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Skawina |
E23073
|
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: Skawina | Statement: [Skawinka River, namedAfter, Skawina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skawina Context triple: [Skawinka River, namedAfter, Skawina]
-
A.
Skawina
chosen
Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
-
B.
Wiślica
Wiślica is a historic town in south-central Poland, known for its medieval architecture and archaeological significance as one of the country’s oldest settlements.
-
C.
Supraśl
Supraśl is a small historic spa town in northeastern Poland, known for its Orthodox monastery complex and picturesque setting along the Supraśl River.
-
D.
Byczyna
Byczyna is a historic small town in southwestern Poland known for its well-preserved medieval urban layout and defensive walls.
-
E.
Trzciana
Trzciana is a village in southern Poland historically notable as the site of the 1629 Battle of Trzciana during the Polish–Swedish War.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e48c0208190bb7ec80780480b37 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e266000c8190b0ba4c9e63ba0542 |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 8:38 p.m.