Triple
T16327370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blšanka |
E396456
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | cs:Blšanka |
E396456
|
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: cs:Blšanka | Statement: [Blšanka, hasNameInLanguage, cs:Blšanka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: cs:Blšanka Context triple: [Blšanka, hasNameInLanguage, cs:Blšanka]
-
A.
Blšanka
chosen
Blšanka is a small river in the Czech Republic that flows through the Ústí nad Labem and Karlovy Vary regions before joining the Ohře River.
-
B.
Blansko
Blansko is a small industrial town in the South Moravian Region of the Czech Republic, known as a gateway to the Moravian Karst cave system.
-
C.
Blatná
Blatná is a historic Czech town best known for its picturesque water castle and surrounding ponds in the South Bohemian countryside.
-
D.
Ploučnice
Ploučnice is a river in the northern Czech Republic that flows through the Ústí nad Labem Region before joining the Elbe.
-
E.
Blešno
Blešno is a small village and municipality in the Hradec Králové Region of the Czech Republic.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dcd034819081d849003d918245 |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00260f487c81909e3e54e47c11b83a |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 5:07 a.m.