Triple
T14011964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Beskids |
E337102
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Żywiec |
—
|
NE NERFINISHED |
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: Żywiec | Statement: [Little Beskids, hasTown, Żywiec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Żywiec Context triple: [Little Beskids, hasTown, Żywiec]
-
A.
Żywiec
chosen
Żywiec is a historic town in southern Poland best known for its long-standing brewery and picturesque location in the Beskid Mountains.
-
B.
Zbrzyca
Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
-
C.
Inowrocław
Inowrocław is a historic spa and industrial city in north-central Poland, known for its saltworks and location in the Kuyavia region.
-
D.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
-
E.
Jaworzno
Jaworzno is a city in southern Poland, located in the Silesian Voivodeship and known for its industrial heritage and role in the Upper Silesian urban area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed5cfd0819085b9c860b119a9de |
completed | April 14, 2026, 12:11 p.m. |
Created at: April 9, 2026, 10:19 p.m.