Triple

T7933154
Position Surface form Disambiguated ID Type / Status
Subject Artifact Registry E184228 entity
Predicate supportsOrganizationPolicyConstraint P79852 FINISHED
Object restricting artifact locations 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: restricting artifact locations | Statement: [Artifact Registry, supportsOrganizationPolicyConstraint, restricting artifact locations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOrganizationPolicyConstraint
Context triple: [Artifact Registry, supportsOrganizationPolicyConstraint, restricting artifact locations]
  • A. hasPolicySupport
    Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
  • B. supportsPolicy
    Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
  • C. containsPolicyOn
    Indicates that one entity includes, references, or incorporates a specific policy within it.
  • D. hasEnrollmentPolicy
    Indicates that there is a specific rule or set of rules governing who may enroll in, access, or participate in something and under what conditions.
  • E. supportsOrganizationUseCase
    Indicates that one entity provides the necessary functionality or conditions for an organization to carry out a specific use case or operational scenario.
  • F. None of above. chosen

Provenance (4 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3acfd2a88190b1a13cd6fdedc272 completed March 31, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69cae9335f288190ba96781fd6576a2b completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf7882b048190baa333af9f698590 completed March 30, 2026, 10:22 p.m.
Created at: March 30, 2026, 5:08 p.m.