Triple
T11161983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jastrzębie-Zdrój |
E264057
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Rybnik |
E351435
|
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: Rybnik | Statement: [Jastrzębie-Zdrój, hasNearbyCity, Rybnik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rybnik Context triple: [Jastrzębie-Zdrój, hasNearbyCity, Rybnik]
-
A.
Rybnik
chosen
Rybnik is a significant industrial and cultural city in the Silesian region of southern Poland, known for its coal mining heritage and regional economic importance.
-
B.
Dąbie
Dąbie is a small town in central Poland, located in the Łódź Voivodeship along the Ner River.
-
C.
Skawina
Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
-
D.
Trzciana
Trzciana is a village in southern Poland historically notable as the site of the 1629 Battle of Trzciana during the Polish–Swedish War.
-
E.
Bóbrka
Bóbrka is a village in southeastern Poland historically significant as one of the birthplaces of the modern oil industry.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8832fe88190a74d81f9ed547baa |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e46375c61c8190939401f790cf1593 |
completed | April 19, 2026, 5:09 a.m. |
Created at: April 8, 2026, 9:29 p.m.