Triple
T8410673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krapivensky Uyezd |
E198613
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Krapivna |
E734796
|
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: Krapivna | Statement: [Krapivensky Uyezd, namedAfter, Krapivna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krapivna Context triple: [Krapivensky Uyezd, namedAfter, Krapivna]
-
A.
Krapivna
chosen
Krapivna is a historic Russian town that once served as an administrative center in the Tula region.
-
B.
Pervomaiskyi
Pervomaiskyi is a small industrial city in eastern Ukraine known for its chemical industry and location within Kharkiv Oblast.
-
C.
Kolodiazhne
Kolodiazhne is a village in northwestern Ukraine known for being closely associated with the life and creative work of the renowned poet Lesya Ukrainka.
-
D.
Zhmerynka
Zhmerynka is a city in central Ukraine known as an important regional railway junction and administrative center.
-
E.
Demänovka
Demänovka is a river in the Liptov region of northern Slovakia, known for flowing through the Demänovská Valley in the Low Tatras.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83dec1f08190ae08719e860b29fa |
completed | March 31, 2026, 8:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4db075c881909083b3384fcde344 |
completed | April 2, 2026, 11:06 a.m. |
Created at: March 30, 2026, 6:05 p.m.