Triple
T33332597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet economy |
E853446
|
entity |
| Predicate | firstMajorPlan |
P192359
|
FINISHED |
| Object | First Five-Year Plan |
E1750
|
NE 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: First Five-Year Plan | Statement: [Soviet economy, firstMajorPlan, First Five-Year Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorPlan Context triple: [Soviet economy, firstMajorPlan, First Five-Year Plan]
-
A.
majorPlan
chosen
Indicates that an entity serves as a primary or central plan guiding major actions, decisions, or developments related to another entity.
-
B.
firstMajorDevelopment
Indicates that the object is the earliest significant development, milestone, or major advancement associated with the subject.
-
C.
firstMajorSuccess
Indicates that an entity represents the earliest significant achievement or breakthrough in another entity’s career, activity, or development.
-
D.
firstMajorDescription
Indicates that the object is the primary or earliest major field of study associated with the subject.
-
E.
firstMajorRoute
Indicates that the specified route is the primary or earliest major route associated with an entity (such as a location, project, or network).
- F. None of above.
Provenance (4 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3576dad3bc819095219b8d63f7138d |
completed | June 19, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:34 a.m.