Triple
T8773193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala Legislative Assembly |
E208513
|
entity |
| Predicate | budgetSession |
P85318
|
FINISHED |
| Object | held annually |
—
|
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: held annually | Statement: [Kerala Legislative Assembly, budgetSession, held annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetSession Context triple: [Kerala Legislative Assembly, budgetSession, held annually]
-
A.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
B.
budgetFunction
Indicates a relationship where a specific budgeting rule or formula determines how resources or funds are allocated or constrained for an entity or activity.
-
C.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
D.
budgetRight
Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
-
E.
budgetScope
Indicates the extent or range of financial resources allocated or considered within a particular budget.
- F. None of above. chosen
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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:41 p.m.