Triple
T22967261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hlukhiv Uyezd |
E571079
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Hlukhiv |
—
|
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: Hlukhiv | Statement: [Hlukhiv Uyezd, namedAfter, Hlukhiv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hlukhiv Context triple: [Hlukhiv Uyezd, namedAfter, Hlukhiv]
-
A.
Hlukhiv
chosen
Hlukhiv is a historic city in northern Ukraine that served as an important political and cultural center of the Cossack Hetmanate in the 18th century.
-
B.
Khmilnyk
Khmilnyk is a spa and resort town in central Ukraine known for its radon mineral waters and therapeutic health facilities.
-
C.
Chernihiv
Chernihiv is a historic city in northern Ukraine known for its ancient churches, rich cultural heritage, and role as a regional administrative and memorial center.
-
D.
Horokhiv
Horokhiv is a small town in western Ukraine known for its location within the historic Volyn region.
-
E.
Okhtyrka
Okhtyrka is a historic city in northeastern Ukraine known as one of the principal centers of the Sloboda Ukraine region.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1822f57088190addc6857063b4cca |
completed | April 29, 2026, 3:59 a.m. |
Created at: April 17, 2026, 3:48 p.m.