Triple
T7639285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lučina |
E172957
|
entity |
| Predicate | hasCityOnRiver |
P17819
|
FINISHED |
| Object | Havířov |
E683386
|
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: Havířov | Statement: [Lučina, hasCityOnRiver, Havířov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Havířov Context triple: [Lučina, hasCityOnRiver, Havířov]
-
A.
Havířov
chosen
Havířov is an industrial city in the Moravian-Silesian Region of the Czech Republic, known as one of the country’s youngest cities and a post-war planned urban center.
-
B.
Přerov
Přerov is a city in the Olomouc Region of the Czech Republic, known as an important industrial and transport hub on the Bečva River.
-
C.
Prostějov
Prostějov is a historic city in the Olomouc Region of the Czech Republic known for its long-standing textile industry and Central European cultural heritage.
-
D.
Litoměřice
Litoměřice is a historic town in the Ústí nad Labem Region of the Czech Republic, known for its well-preserved architecture and location at the confluence of the Elbe and Ohře rivers.
-
E.
Chrudim
Chrudim is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved medieval center and cultural heritage.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facc4b5481908697e662b0991e3f |
completed | March 27, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b4f48de88190b9cf40bfb1a26323 |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 3:57 p.m.