Triple
T5739733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appropriation Bill (India) |
E126583
|
entity |
| Predicate | typeOfExpenditure |
P62936
|
FINISHED |
| Object | revenue expenditure |
—
|
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: revenue expenditure | Statement: [Appropriation Bill (India), typeOfExpenditure, revenue expenditure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfExpenditure Context triple: [Appropriation Bill (India), typeOfExpenditure, revenue expenditure]
-
A.
mainExpenditureCategory
chosen
Indicates the primary type or classification of spending to which a particular expenditure mainly belongs.
-
B.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
C.
reimbursementCategory
Indicates the classification or type under which a reimbursement claim or expense is categorized.
-
D.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
E.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255f302c819094f97b4defeded07 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.