Triple

T6733088
Position Surface form Disambiguated ID Type / Status
Subject RET E153683 entity
Predicate regulatesSafety P20206 FINISHED
Object Dutch transport 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: Dutch transport safety regulations | Statement: [RET, regulatesSafety, Dutch transport safety regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatesSafety
Context triple: [RET, regulatesSafety, Dutch transport safety regulations]
  • A. safetyRegulationEffect
    Indicates how a safety regulation influences or changes the conditions, behaviors, or outcomes associated with the regulated entities.
  • B. hasSafetyRegulationCompliance
    Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
  • C. safetyRegulationChange
    Indicates a modification, update, or revision to existing safety regulations governing how something must be designed, operated, or managed.
  • D. safetyRequirement chosen
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • E. regulatesIn
    Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
  • 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_69c6880bdd68819097de8b6099992682 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d354177481908ab3cf5437c095e2 completed March 27, 2026, 6:58 p.m.
PD Predicate disambiguation batch_69c6d08e8a2c8190ae4e8d8c039be7ce completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:09 p.m.