Triple
T6656664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarnów County |
E150961
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Radłów |
E512586
|
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: Radłów | Statement: [Tarnów County, containsSettlement, Radłów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Radłów Context triple: [Tarnów County, containsSettlement, Radłów]
-
A.
Radłów
chosen
Radłów is a small town in southern Poland known for its historical ties to the Lesser Poland region and its proximity to the city of Tarnów.
-
B.
Limanowa
Limanowa is a small town in southern Poland, located in the Lesser Poland Voivodeship, known for its historical significance and picturesque mountainous surroundings.
-
C.
Zułów
Zułów is a village in present-day Lithuania best known as the birthplace of Polish statesman and military leader Józef Piłsudski.
-
D.
Rakoń
Rakoń is a mountain peak in the Western Tatras on the Polish-Slovak border, popular with hikers for its scenic ridge views.
-
E.
Żory
Żory is a city in southern Poland known for its historical roots in the Silesian region and its mix of industrial and residential character.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b06dbbf88190b39564a688c25a24 |
completed | March 27, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6ef028ccc8190a56395075c9aabf7 |
completed | March 27, 2026, 8:56 p.m. |
Created at: March 27, 2026, 2:01 p.m.