Triple

T36076883
Position Surface form Disambiguated ID Type / Status
Subject Grimsby and Immingham Electric Railway E1043518 entity
Predicate servedWorkforce P36154 FINISHED
Object dock workers at Immingham 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: dock workers at Immingham | Statement: [Grimsby and Immingham Electric Railway, servedWorkforce, dock workers at Immingham]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedWorkforce
Context triple: [Grimsby and Immingham Electric Railway, servedWorkforce, dock workers at Immingham]
  • A. associatedWithWorkforce chosen
    Indicates a relationship in which an entity is connected or related to a particular workforce, such as its members, activities, or management.
  • B. employedPeople
    Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
  • C. hasWorkforceType
    Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
  • D. workforceOrigin
    Indicates the source or place from which a workforce or labor force originates.
  • E. employedApproximately
    Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
  • 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_69f76e3154908190a6f702671c2bea08 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a0031ed5d708190ab93516ad081ada6 completed May 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_6a0031b5dbd081908eb0f4dbb8a0eac3 completed May 10, 2026, 7:20 a.m.
Created at: May 3, 2026, 4:08 p.m.