Triple

T7941375
Position Surface form Disambiguated ID Type / Status
Subject Form 940 E184398 entity
Predicate extendedDueDateRule P32455 FINISHED
Object February 10 if all FUTA tax was deposited on time 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: February 10 if all FUTA tax was deposited on time | Statement: [Form 940, extendedDueDateRule, February 10 if all FUTA tax was deposited on time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extendedDueDateRule
Context triple: [Form 940, extendedDueDateRule, February 10 if all FUTA tax was deposited on time]
  • A. extensionEffectiveDate chosen
    Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
  • B. extendedFor
    Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
  • C. extendsUntil
    Indicates that something continues or remains in effect up to a specified point or limit in time or space.
  • D. endedDueTo
    Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
  • E. extendedBy
    Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
  • 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_69ca8291c2008190b1b8832c87814bcf completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b0c16b8819093c5d1719cd65ee3 completed March 31, 2026, 3:10 a.m.
PD Predicate disambiguation batch_69cae93526d081909303265bf60419fd completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:09 p.m.