Triple

T4328347
Position Surface form Disambiguated ID Type / Status
Subject Security Industry Authority E96685 entity
Predicate requiresLicenceFor P9144 FINISHED
Object designated private security activities 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: designated private security activities | Statement: [Security Industry Authority, requiresLicenceFor, designated private security activities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresLicenceFor
Context triple: [Security Industry Authority, requiresLicenceFor, designated private security activities]
  • A. requiresLicenseOf
    Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
  • B. licenseFor
    Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
  • C. supportsLicense
    Indicates that one entity is compatible with, enables, or is configured to work under a specified license.
  • D. requiresLicenseForPractice chosen
    Indicates that engaging in the specified professional practice is legally contingent upon holding a valid license.
  • E. licenseEnforced
    Indicates that a license’s terms or restrictions are actively applied and upheld in relation to the associated entity or activity.
  • 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_69b34542fd908190b11b08faad8decfd completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35133688c8190ab5527ae01748f13 completed March 12, 2026, 11:50 p.m.
PD Predicate disambiguation batch_69b34f4e13fc8190a42c519f37959d27 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:13 p.m.