Triple
T17655318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuřim |
E429606
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Ivanychi |
—
|
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: Ivanychi | Statement: [Kuřim, hasTwinTown, Ivanychi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ivanychi Context triple: [Kuřim, hasTwinTown, Ivanychi]
-
A.
Ivanychi
chosen
Ivanychi is a small urban-type settlement in western Ukraine that serves as a local administrative and community center within Volyn Oblast.
-
B.
Yaropolch
Yaropolch is a village in Russia historically noted as the place where Ukrainian Hetman Petro Doroshenko died.
-
C.
Zolotonosha
Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
-
D.
Zhukovka
Zhukovka is a rural locality in Moscow Oblast, Russia, situated within the Odintsovsky District and known primarily as a residential settlement near Moscow.
-
E.
Terebovlia
Terebovlia is a historic town in western Ukraine known for its medieval fortress ruins and role as a regional cultural center.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e40e344819086a49c69f8f2956b |
completed | April 19, 2026, 5:55 a.m. |
Created at: April 10, 2026, 6:06 a.m.