Triple

T18042104
Position Surface form Disambiguated ID Type / Status
Subject Private Security Industry Act 2001 E431675 entity
Predicate createsRegulatorFor P111583 FINISHED
Object private security industry 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: private security industry | Statement: [Private Security Industry Act 2001, createsRegulatorFor, private security industry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: createsRegulatorFor
Context triple: [Private Security Industry Act 2001, createsRegulatorFor, private security industry]
  • A. regulatorCreatedFor chosen
    Indicates that a regulatory body or authority was established specifically to oversee, manage, or enforce rules for a particular entity, activity, or domain.
  • B. regulatorEstablished
    Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
  • C. regulatorType
    Indicates the specific kind or category of regulatory role or authority associated with an entity.
  • D. regulatorRole
    Indicates that one entity serves in an official capacity to oversee, control, or enforce rules and standards governing another entity or activity.
  • E. regulatorAction
    Indicates an action taken by a regulatory authority toward an entity, such as enforcing rules, issuing directives, or applying sanctions.
  • 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_69d8b906482481908183315b9ecf9994 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4bfef454c8190ad3787502f2bdd34 completed April 19, 2026, 11:43 a.m.
PD Predicate disambiguation batch_69e3f908da508190a088aa837ea5b7af completed April 18, 2026, 9:35 p.m.
Created at: April 10, 2026, 10:25 a.m.