Triple
T19885337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikołów County |
E477882
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Rybnik |
—
|
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: Rybnik | Statement: [Mikołów County, borderedBy, Rybnik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rybnik Context triple: [Mikołów County, borderedBy, 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.
Rudny
Rudny is an industrial city in northern Kazakhstan known for its mining activities, particularly iron ore extraction.
-
C.
Dąbie
Dąbie is a small town in central Poland, located in the Łódź Voivodeship along the Ner River.
-
D.
Dąbie
Dąbie is a settlement in Poland that serves as one of the localities within the administrative district of Gmina Dąbie.
-
E.
Chojnik
Chojnik is a village in northern Poland located within the administrative district of Gmina Morąg in the Warmian-Masurian Voivodeship.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659093df081909d3be9c3caeb79ba |
completed | April 20, 2026, 4:49 p.m. |
Created at: April 10, 2026, 1:52 p.m.