Triple
T17655333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuřim |
E429606
|
entity |
| Predicate | hasCadastralArea |
P90148
|
FINISHED |
| Object | Kuřim |
—
|
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: Kuřim | Statement: [Kuřim, hasCadastralArea, Kuřim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuřim Context triple: [Kuřim, hasCadastralArea, Kuřim]
-
A.
Kuřim
chosen
Kuřim is a small industrial town in the South Moravian Region of the Czech Republic, located just northwest of Brno.
-
B.
Topľa
Topľa is a river in eastern Slovakia that flows through the Prešov Region before joining the Ondava River.
-
C.
Kockasti
Kockasti is the popular nickname of the Croatia men's national basketball team, referencing the iconic red-and-white checkered pattern associated with Croatian sports.
-
D.
Vrútky
Vrútky is a town in northern Slovakia that serves as an important railway junction and gateway between central and northern regions of the country.
-
E.
Weißer Kocher
Weißer Kocher is one of the two headstreams that form the Kocher River in the German state of Baden-Württemberg.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e40e344819086a49c69f8f2956b |
completed | April 19, 2026, 5:55 a.m. |
Created at: April 10, 2026, 6:06 a.m.