Triple
T1686576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voronezh |
E36454
|
entity |
| Predicate | hasSisterCity |
P919
|
FINISHED |
| Object | Brno |
E47149
|
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: Brno | Statement: [Voronezh, hasSisterCity, Brno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brno Context triple: [Voronezh, hasSisterCity, Brno]
-
A.
Brno
chosen
Brno is the second-largest city in the Czech Republic, known as a major cultural, educational, and industrial center in the historical region of Moravia.
-
B.
Kolín
Kolín is a historic industrial town and important transport hub on the Elbe River in the Central Bohemian Region of the Czech Republic.
-
C.
Ostrava
Ostrava is a major industrial and cultural city in the northeastern Czech Republic, near the borders with Poland and Slovakia.
-
D.
Olomouc
Olomouc is a historic city in the eastern Czech Republic known for its well-preserved old town, Baroque architecture, and UNESCO-listed Holy Trinity Column.
-
E.
Plzeň
Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa6293c368819094ab0f615e418647 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebef5ac7c81908015969c04fcc425 |
completed | March 9, 2026, 12:37 p.m. |
Created at: March 4, 2026, 7:29 p.m.