Triple
T21184917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far North Construction Trust |
E522055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NKVD-run organization |
C10586
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: NKVD-run organization Context triple: [Far North Construction Trust, instanceOf, NKVD-run organization]
-
A.
NKVD officer
An NKVD officer is a member of the Soviet Union’s internal security and secret police organization responsible for intelligence, political repression, and enforcement of state control during the Stalinist era.
-
B.
Soviet organization
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
-
C.
Gulag administrative body
chosen
The Gulag administrative body is the centralized state organization responsible for planning, managing, and overseeing the operation of forced labor camps within the Soviet penal system.
-
D.
Rusyn organization
A Rusyn organization is a formal group or institution dedicated to representing, preserving, and promoting the cultural, social, political, or educational interests of the Rusyn people.
-
E.
Cheka officer
A Cheka officer is a member of the early Soviet secret police responsible for internal security, political repression, and the suppression of perceived enemies of the Bolshevik regime.
- F. None of above.
Provenance (1 batch)
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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:06 p.m.