Triple
T33719428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state budget of Lithuania |
E863969
|
entity |
| Predicate | expenditureComponent |
P62936
|
FINISHED |
| Object | education spending |
—
|
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: education spending | Statement: [state budget of Lithuania, expenditureComponent, education spending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expenditureComponent Context triple: [state budget of Lithuania, expenditureComponent, education spending]
-
A.
expenditureFor
Indicates a relationship where a specific expenditure is made or allocated for a particular purpose, item, project, or entity.
-
B.
expenditures
Indicates that an entity spends or allocates money or resources, typically specifying the amount, purpose, or category of that spending.
-
C.
expenditureDrawnBy
Indicates that a particular expenditure is initiated, authorized, or incurred by a specific entity.
-
D.
mainExpenditureCategory
chosen
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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae8ee40819089a1ea4f3727513b |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.