Triple
T19249102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horodnia Raion |
E481341
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Horodnia |
—
|
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: Horodnia | Statement: [Horodnia Raion, namedAfter, Horodnia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horodnia Context triple: [Horodnia Raion, namedAfter, Horodnia]
-
A.
Horodnia
chosen
Horodnia is a small town in northern Ukraine known for its historical roots and location within the Chernihiv region.
-
B.
Novogrudok
Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
-
C.
Zhlobin
Zhlobin is an industrial city in southeastern Belarus, known especially for its major steel production facilities and location on the Dnieper River.
-
D.
Horodok
Horodok is a small town in western Ukraine known for its historical roots and location within the Khmelnytskyi region.
-
E.
Lokhvytsia
Lokhvytsia is a town in central Ukraine, historically part of the Poltava region and known for its role in regional trade and agriculture.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2f43e48190abab5257bec8e6aa |
completed | April 20, 2026, 10:08 a.m. |
Created at: April 10, 2026, 1:27 p.m.