Triple
T37321846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Group Insurance Program of Florida |
E926501
|
entity |
| Predicate | benefitYear |
P92184
|
FINISHED |
| Object | calendar 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: calendar year | Statement: [State Group Insurance Program of Florida, benefitYear, calendar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitYear Context triple: [State Group Insurance Program of Florida, benefitYear, calendar year]
-
A.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
C.
appliesInYears
chosen
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
D.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
E.
agreementYear
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.