Triple
T21998465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vote on Account (India) |
E543263
|
entity |
| Predicate | financialYearContext |
P8230
|
FINISHED |
| Object | used at the beginning of a financial year |
—
|
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: used at the beginning of a financial year | Statement: [Vote on Account (India), financialYearContext, used at the beginning of a financial year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialYearContext Context triple: [Vote on Account (India), financialYearContext, used at the beginning of a financial year]
-
A.
financialYearStart
Indicates the date or point in time when an entity’s financial or fiscal year begins.
-
B.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
C.
budgetFiscalYear
chosen
Indicates the fiscal year to which a particular budget or budgeting activity applies.
-
D.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
E.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276774508190b96870266e10979a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.