Triple
T5476089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Carolina General Assembly |
E122956
|
entity |
| Predicate | fiscalYearStartInfluence |
P63981
|
FINISHED |
| Object | sets state fiscal policy |
—
|
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: sets state fiscal policy | Statement: [South Carolina General Assembly, fiscalYearStartInfluence, sets state fiscal policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalYearStartInfluence Context triple: [South Carolina General Assembly, fiscalYearStartInfluence, sets state fiscal policy]
-
A.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
-
B.
budgetFiscalYear
Indicates the fiscal year to which a particular budget or budgeting activity applies.
-
C.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
D.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
E.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923639bc81909a83dd4fcaa8c636 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.