Triple
T9024074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet design institutes |
E215999
|
entity |
| Predicate | usedPlanningHorizon |
P38657
|
FINISHED |
| Object | five-year plans |
—
|
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: five-year plans | Statement: [Soviet design institutes, usedPlanningHorizon, five-year plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPlanningHorizon Context triple: [Soviet design institutes, usedPlanningHorizon, five-year plans]
-
A.
predictionHorizon
Indicates the temporal extent into the future over which a prediction or forecast is intended to apply.
-
B.
goalHorizon
chosen
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
C.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
D.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7a770081908dfe3ce3374a04ba |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.