Triple

T165067
Position Surface form Disambiguated ID Type / Status
Subject Mon Valley Works E2995 entity
Predicate hasLaborForce P3027 FINISHED
Object unionized workforce 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: unionized workforce | Statement: [Mon Valley Works, hasLaborForce, unionized workforce]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLaborForce
Context triple: [Mon Valley Works, hasLaborForce, unionized workforce]
  • A. employedApproximately
    Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
  • B. employedPeople
    Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
  • C. hasEconomicActivity
    Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
  • D. laborSystem chosen
    Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
  • E. hasMajorEmployer
    Indicates that an entity has a primary or most significant employer with which it is chiefly affiliated for work or occupation.
  • 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_69a2524ce1e48190ab066bf72859f474 completed Feb. 28, 2026, 2:26 a.m.
NER Named-entity recognition batch_69a258827da481909b20ea5e9d21676f completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a25664ba8081908ac298511a9fc5ba completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:34 a.m.