Triple
T33332596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet economy |
E853446
|
entity |
| Predicate | firstMajorPlanStartTime |
P4044
|
FINISHED |
| Object | 1928 |
—
|
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: 1928 | Statement: [Soviet economy, firstMajorPlanStartTime, 1928]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorPlanStartTime Context triple: [Soviet economy, firstMajorPlanStartTime, 1928]
-
A.
firstPlanStartYear
chosen
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
B.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
-
C.
firstMajorRevisionDate
Indicates the date on which an entity underwent its first significant or major revision.
-
D.
firstMajorDevelopment
Indicates that the object is the earliest significant development, milestone, or major advancement associated with the subject.
-
E.
seventhPlanStartYear
Indicates the calendar year in which the seventh plan in a sequence officially begins.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:34 a.m.