Triple
T14931245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharkov Governorate |
E372268
|
entity |
| Predicate | includedCity |
P8465
|
FINISHED |
| Object | Izyum |
E1127711
|
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: Izyum | Statement: [Kharkov Governorate, includedCity, Izyum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Izyum Context triple: [Kharkov Governorate, includedCity, Izyum]
-
A.
Ishkur
Ishkur is a Mesopotamian storm and rain god associated with thunder, fertility, and seasonal weather.
-
B.
Izel
Izel is a small village in the Walloon region of Belgium, known for its rural character and location within the municipality of Chiny in the province of Luxembourg.
-
C.
Ihnasya
Ihnasya is a city in Egypt known for its location within the Beni Suef Governorate along the Nile Valley.
-
D.
İmroz
İmroz, now known as Gökçeada, is a large Aegean island of Turkey historically home to a significant Greek community.
-
E.
Izyum Okruha
chosen
Izyum Okruha was an administrative district in early Soviet Ukraine that succeeded part of the former Kharkov Governorate.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e8ac6d08190809045a6d00a3d47 |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 10, 2026, 2:36 a.m.