Triple

T38316284
Position Surface form Disambiguated ID Type / Status
Subject Employee Classification Act E1033833 entity
Predicate intendedToBenefit P79876 FINISHED
Object employees misclassified as independent contractors 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: employees misclassified as independent contractors | Statement: [Employee Classification Act, intendedToBenefit, employees misclassified as independent contractors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedToBenefit
Context triple: [Employee Classification Act, intendedToBenefit, employees misclassified as independent contractors]
  • A. believedBenefit
    Indicates that one entity considers or perceives another entity, action, or state as providing an advantage or positive outcome.
  • B. benefice
    Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
  • C. benefitDesignGoal
    Indicates that something contributes positively toward achieving a particular design goal.
  • D. affectsBenefit
    Indicates that one entity has an influence on, modifies, or determines the benefit or advantage received by another entity.
  • E. intendedWith chosen
    Indicates that one entity is the planned or desired target, recipient, or context for the use or application 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_69f76e132c408190969b3d35c04b87ae completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fe744faca881908e11e90e0a35653f completed May 8, 2026, 11:39 p.m.
PD Predicate disambiguation batch_69fe734cbf7081909a552c5cf3b5ea59 completed May 8, 2026, 11:35 p.m.
Created at: May 3, 2026, 4:30 p.m.