Triple
T27178449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverdlovsk-45 |
E683118
|
entity |
| Predicate | statusAfterUSSR |
P124441
|
FINISHED |
| Object | remained a closed city |
—
|
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: remained a closed city | Statement: [Sverdlovsk-45, statusAfterUSSR, remained a closed city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterUSSR Context triple: [Sverdlovsk-45, statusAfterUSSR, remained a closed city]
-
A.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
B.
postSovietStatus
chosen
Indicates that an entity has a political, social, or historical status related to the period or conditions following the dissolution of the Soviet Union.
-
C.
statusAfterColdWar
Indicates the condition or standing of an entity in the period following the end of the Cold War.
-
D.
roleInUSSRDisintegration
Indicates involvement or contribution of an entity to the political, economic, or social processes that led to the disintegration of the USSR.
-
E.
successorStateOnSovietSide
Indicates that one state is recognized as the political or legal successor to a former state that was part of the Soviet sphere or structure.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 9:27 a.m.