Triple

T16864239
Position Surface form Disambiguated ID Type / Status
Subject Wapping dispute E409996 entity
Predicate employerAction P75129 FINISHED
Object dismissal of striking print workers 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: dismissal of striking print workers | Statement: [Wapping dispute, employerAction, dismissal of striking print workers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employerAction
Context triple: [Wapping dispute, employerAction, dismissal of striking print workers]
  • A. employmentAction chosen
    Indicates an action or event that changes, initiates, or terminates an employment relationship between entities.
  • B. employer
    Indicates a relationship where one entity hires, pays, and oversees the work of another entity.
  • C. employerSide
    Indicates that the subject participates in or represents the employer’s position, interests, or perspective within an employment relationship or dispute.
  • D. employerIn
    Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
  • E. employerSupportFunction
    Indicates that an employer provides supportive functions or services (such as resources, assistance, or benefits) to or on behalf of another party.
  • 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b505a390819097ec31cd210eca60 completed April 18, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69e32b8cbb048190878a259cc5be960e completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:24 a.m.