Triple
T10347085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Český Těšín |
E243777
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Žywiec |
E838198
|
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: Žywiec | Statement: [Český Těšín, hasTwinTown, Žywiec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Žywiec Context triple: [Český Těšín, hasTwinTown, Ž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.
Pszczyna
Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque old town.
-
D.
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.
-
E.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9251654819080d1e3f0ed4ee9d3 |
completed | April 7, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e2527570819092314ee0a678e53c |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 6, 2026, 11:56 a.m.