Triple
T21394386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Česká Lípa |
E527740
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Nový Bor |
—
|
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: Nový Bor | Statement: [Česká Lípa, hasNearbyTown, Nový Bor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nový Bor Context triple: [Česká Lípa, hasNearbyTown, Nový Bor]
-
A.
Nový Bor
chosen
Nový Bor is a Czech town in the Liberec Region known historically for its glassmaking industry and proximity to the Lusatian Mountains.
-
B.
Nové Mesto
Nové Mesto is a borough of Bratislava, Slovakia, known for its mix of residential areas, sports facilities, and commercial zones.
-
C.
Nové Město
Nové Město is a historic central district of Prague known for its important squares, cultural landmarks, and vibrant urban life.
-
D.
Novohrad
Novohrad is a historical and geographical region in southern Slovakia known for its rural landscapes, traditional culture, and border location near Hungary.
-
E.
Nové Hrady
Nové Hrady is a historic town in the Czech Republic known for its well-preserved castle and location near the Austrian border in the South Bohemian Region.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62cd30f08190aba90afed6116a2a |
completed | April 26, 2026, 7:09 p.m. |
Created at: April 16, 2026, 5:13 p.m.