Triple

T17560652
Position Surface form Disambiguated ID Type / Status
Subject PL/Perl E427687 entity
Predicate trustedVariantRestrictions P125239 FINISHED
Object no direct access to the file system 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: no direct access to the file system | Statement: [PL/Perl, trustedVariantRestrictions, no direct access to the file system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trustedVariantRestrictions
Context triple: [PL/Perl, trustedVariantRestrictions, no direct access to the file system]
  • A. isUntrustedVariant
    Indicates that one entity is considered a less reliable, potentially unsafe, or otherwise unverified version or form of another entity.
  • B. securedVariant
    Indicates that one entity is a security-enhanced or more protected version of another entity.
  • C. hasSemanticRestriction
    Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
  • D. policyRestriction chosen
    Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
  • E. notRestrictedBy
    Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e456267e208190a1238fbe1a535bb0 completed April 19, 2026, 4:12 a.m.
PD Predicate disambiguation batch_69e3b4fb39948190a82a597c5bac5c57 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:50 a.m.