Triple

T5502049
Position Surface form Disambiguated ID Type / Status
Subject Freight Operating Companies E144350 entity
Predicate regulationSubject P34837 FINISHED
Object rail safety regulations 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: rail safety regulations | Statement: [Freight Operating Companies, regulationSubject, rail safety regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulationSubject
Context triple: [Freight Operating Companies, regulationSubject, rail safety regulations]
  • A. subjectToRegulation chosen
    Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
  • B. regulationAtIssue
    Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
  • C. relatedRegulation
    Indicates that there exists a regulatory rule, law, or directive that is associated with, governs, or is otherwise relevant to the referenced entity or activity.
  • D. alsoRegulates
    Indicates that an entity not only has a primary regulatory effect on a target but additionally regulates that same target through another, supplementary regulatory relationship.
  • E. regulationImpact
    Indicates how a regulation influences, constrains, or alters the behavior, performance, or outcomes associated with the related entities.
  • 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_69c008f5a2748190bce7a39aabf87a6d completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f0a512c81908f077378917e5879 completed March 22, 2026, 4:55 p.m.
PD Predicate disambiguation batch_69c01b052f3c81909f71c6add0f35a6f completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:32 p.m.