Triple

T29229175
Position Surface form Disambiguated ID Type / Status
Subject Pittston Coal Company E741019 entity
Predicate laborDisputeStart P126347 FINISHED
Object 1989 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: 1989 | Statement: [Pittston Coal Company, laborDisputeStart, 1989]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laborDisputeStart
Context triple: [Pittston Coal Company, laborDisputeStart, 1989]
  • A. laborRelationsIssue
    Indicates a relationship where there is a dispute, concern, or matter involving labor relations between workers (or their representatives) and employers.
  • B. disputeBegan chosen
    Indicates that a conflict or disagreement between parties was initiated or came into existence at a specific point in time.
  • C. occupationBegan
    Indicates the point in time when an entity started holding a particular occupation or job.
  • D. mainLaborLaw
    Indicates that the referenced law is the primary or governing labor/employment law applicable to the situation or entities involved.
  • E. laborUnion
    Indicates that an entity is a labor union representing workers in collective employment-related matters.
  • 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_69f07cbb12bc81908c1971d9de9a8d2a completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6645ba71c81908044ade6ab577018 completed May 2, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f663362c008190a22afed262f1e426 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 12:18 p.m.