Triple
T87087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-Year Plans for the National Economy of the Soviet Union |
E1750
|
entity |
| Predicate | twelfthPlanStartYear |
P3297
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Five-Year Plans for the National Economy of the Soviet Union, twelfthPlanStartYear, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twelfthPlanStartYear Context triple: [Five-Year Plans for the National Economy of the Soviet Union, twelfthPlanStartYear, 1986]
-
A.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
B.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
C.
developedAt
Indicates the place or location where something was created, built, or developed.
-
D.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
E.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2503d304c8190a0034ffa4a38a501 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb6da2c8190a33d144d219f7abe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.