Triple
T3963967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraków County |
E85970
|
entity |
| Predicate | contains |
P35
|
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: [Kraków County, contains, Skawina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skawina Context triple: [Kraków County, contains, 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.
Mława
Mława is a town in north-central Poland known for its historical significance, including a major World War II battle, and its regional cultural and economic role.
-
C.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
E.
Rakoń
Rakoń is a mountain peak in the Western Tatras on the Polish-Slovak border, popular with hikers for its scenic ridge views.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef97326888190bbfe15b218e3112e |
completed | March 9, 2026, 4:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b55619cb548190ac2553f23de9bfed |
completed | March 14, 2026, 12:35 p.m. |
Created at: March 9, 2026, 3:31 p.m.