Triple
T24909966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | областьПротеканияВРоссии |
P127825
|
FINISHED |
| Object | Калининградская область |
—
|
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: Калининградская область | Statement: [Шешупе, областьПротеканияВРоссии, Калининградская область]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: областьПротеканияВРоссии Context triple: [Шешупе, областьПротеканияВРоссии, Калининградская область]
-
A.
locatedInRegionOfRussia
chosen
Indicates that one entity is geographically situated within a specified region of Russia.
-
B.
регионДеятельности
Indicates the geographic region or area in which an entity carries out its activities or operations.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
E.
RussiaControls
Indicates that Russia exercises authority, influence, or governing power over the specified entity or territory.
- F. None of above.
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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4236e93c081908876aff0a06ed21a |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.