Triple
T25064171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State budget of West Virginia |
E627738
|
entity |
| Predicate | fiscalPeriod |
P142377
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [State budget of West Virginia, fiscalPeriod, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalPeriod Context triple: [State budget of West Virginia, fiscalPeriod, annual]
-
A.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
B.
fiscalYearDuration
chosen
Indicates the length of time that a fiscal year spans, typically expressed as a specific duration or number of months.
-
C.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
D.
fiscalYearLabel
Indicates the specific fiscal year designation associated with an entity or record.
-
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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599c81148190b84e8d46368a6677 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:10 a.m.