Triple
T10083124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherkasy Oblast |
E213950
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Zolotonosha |
E544208
|
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: Zolotonosha | Statement: [Cherkasy Oblast, contains, Zolotonosha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zolotonosha Context triple: [Cherkasy Oblast, contains, Zolotonosha]
-
A.
Zolotonosha
chosen
Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
-
B.
Zhukovka
Zhukovka is a rural locality in Moscow Oblast, Russia, situated within the Odintsovsky District and known primarily as a residential settlement near Moscow.
-
C.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
-
D.
Maloyaroslavets
Maloyaroslavets is a historic town in western Russia known for the 1812 Battle of Maloyaroslavets during Napoleon’s invasion.
-
E.
Luzhitsy
Luzhitsy is a rural village in northwestern Russia historically associated with the Votic people and their traditional language and culture.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04352d081908f676444cd2d2578 |
completed | April 2, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d30050fbec8190ab7807d64ab73e61 |
completed | April 6, 2026, 12:37 a.m. |
Created at: March 30, 2026, 9 p.m.