Triple
T34746770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korcheva |
E1001657
|
entity |
| Predicate | wasResettledTo |
P1660
|
FINISHED |
| Object | nearby settlements on the shore of Ivankovo Reservoir |
—
|
LITERAL 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: nearby settlements on the shore of Ivankovo Reservoir | Statement: [Korcheva, wasResettledTo, nearby settlements on the shore of Ivankovo Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasResettledTo Context triple: [Korcheva, wasResettledTo, nearby settlements on the shore of Ivankovo Reservoir]
-
A.
wasReconfiguredIn
Indicates that an entity underwent a change in its configuration or setup during a specified time or event.
-
B.
hasResettlementRole
Indicates that an entity holds a specific role, responsibility, or function within a resettlement process or program.
-
C.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
D.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.