Triple

T5929317
Position Surface form Disambiguated ID Type / Status
Subject Annual Enrollment Period E131894 entity
Predicate decisionEffectiveDate P66767 FINISHED
Object changes take effect at the start of the next coverage 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: changes take effect at the start of the next coverage year | Statement: [Annual Enrollment Period, decisionEffectiveDate, changes take effect at the start of the next coverage year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decisionEffectiveDate
Context triple: [Annual Enrollment Period, decisionEffectiveDate, changes take effect at the start of the next coverage year]
  • A. decisionDate
    Indicates the date on which a specific decision was formally made or finalized.
  • B. dateEnacted
    Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
  • C. effectiveFor
    Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
  • D. approvalDate
    Indicates the date on which an action, request, or item was formally approved.
  • E. dateOfEnactment
    Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
  • 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_69c0085b75e88190a632f9691f9da48b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03c9239e08190bff7ef2bd6d21ae0 completed March 22, 2026, 7:01 p.m.
PD Predicate disambiguation batch_69c033541d108190a34d1fde2fe9dacb completed March 22, 2026, 6:22 p.m.
PDg Predicate description generation batch_69c03c8d579081909d7b97fc9014b5d7 completed March 22, 2026, 7:01 p.m.
Created at: March 22, 2026, 4 p.m.