Triple
T20986131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State budget of Louisiana |
E516895
|
entity |
| Predicate | fiscalYearDuration |
P142377
|
FINISHED |
| Object | 1 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: 1 year | Statement: [State budget of Louisiana, fiscalYearDuration, 1 year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalYearDuration Context triple: [State budget of Louisiana, fiscalYearDuration, 1 year]
-
A.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
B.
financialYearStart
Indicates the date or point in time when an entity’s financial or fiscal year begins.
-
C.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
-
D.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
E.
hasFiscalYearCoverage
Indicates that one entity’s applicable period, data, or responsibility spans or corresponds to a specified fiscal year or range of fiscal years.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe31cec8190a1007414148b8abe |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:48 p.m.