Triple
T21508986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state budget of the USSR |
E530666
|
entity |
| Predicate | expenditureItem |
P71941
|
FINISHED |
| Object | heavy industry |
—
|
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: heavy industry | Statement: [state budget of the USSR, expenditureItem, heavy industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expenditureItem Context triple: [state budget of the USSR, expenditureItem, heavy industry]
-
A.
expenditureFor
chosen
Indicates a relationship where a specific expenditure is made or allocated for a particular purpose, item, project, or entity.
-
B.
budgetItemOf
Indicates that one entity is a specific budget line or allocation that belongs to, or is part of, another entity’s overall budget.
-
C.
expenditures
Indicates that an entity spends or allocates money or resources, typically specifying the amount, purpose, or category of that spending.
-
D.
mainExpenditureCategory
Indicates the primary type or classification of spending to which a particular expenditure mainly belongs.
-
E.
expendedAs
Indicates that a resource, amount, or asset is used up, spent, or consumed in the form of another specified entity or purpose.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea84042481909b43a7a4c5d2336a |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.