Triple
T33553431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narkomzem Building, Moscow |
E859399
|
entity |
| Predicate | designedForRegime |
P197712
|
FINISHED |
| Object | Soviet socialist state |
—
|
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: Soviet socialist state | Statement: [Narkomzem Building, Moscow, designedForRegime, Soviet socialist state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForRegime Context triple: [Narkomzem Building, Moscow, designedForRegime, Soviet socialist state]
-
A.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
B.
targetedRegime
Indicates that an entity intentionally directed actions, policies, or operations against a particular governing regime.
-
C.
regimeDescription
Indicates that an entity provides a textual characterization or explanation of a particular regime, system, or governing arrangement.
-
D.
regimeCharacterizedAs
Indicates that a political or governance regime is described or classified as having a particular character, quality, or type.
-
E.
settingRegime
Indicates the regulatory, policy, or rule-based framework under which an action, process, or relationship is carried out.
- F. None of above. chosen
Provenance (4 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:40 a.m.