Triple
T947837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet government |
E20452
|
entity |
| Predicate | reorganizationDate |
P5212
|
FINISHED |
| Object | 1922 |
—
|
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: 1922 | Statement: [Soviet government, reorganizationDate, 1922]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizationDate Context triple: [Soviet government, reorganizationDate, 1922]
-
A.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
B.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
C.
reformDate
chosen
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
D.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
E.
isPartOfReorganization
Indicates that an entity is involved in, or belongs to, a structural or organizational reconfiguration process.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3be19448190a8863fce3d152430 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.