Triple
T13459116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Świdnica |
E311312
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Jičín |
E305393
|
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: Jičín | Statement: [Świdnica, twinTown, Jičín]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jičín Context triple: [Świdnica, twinTown, Jičín]
-
A.
Jičín
chosen
Jičín is a historic town in the Czech Republic known for its well-preserved medieval center and association with the fairy-tale character Rumcajs.
-
B.
Nymburk
Nymburk is a historic town in the Czech Republic known for its medieval fortifications and location on the Elbe River.
-
C.
Žatec
Žatec is a historic Czech town in the Ústí nad Labem Region renowned for its long-standing hop-growing tradition and beer production.
-
D.
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.
-
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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0c177081909178dec61b09c278 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe249c57bc819089baed544fb8fead |
completed | May 8, 2026, 5:59 p.m. |
Created at: April 9, 2026, 9:41 p.m.