Triple

T28610270
Position Surface form Disambiguated ID Type / Status
Subject Yama E724151 entity
Predicate defaultPolicy P103767 FINISHED
Object allow ptrace with traditional restrictions when scope is 0 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: allow ptrace with traditional restrictions when scope is 0 | Statement: [Yama, defaultPolicy, allow ptrace with traditional restrictions when scope is 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defaultPolicy
Context triple: [Yama, defaultPolicy, allow ptrace with traditional restrictions when scope is 0]
  • A. publicPolicy
    Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
  • B. defaultOn
    Indicates that something is in an enabled or active state by default, without requiring explicit activation.
  • C. typicalPolicyPreference
    Indicates that one entity’s policy preference is characteristic or representative of what is usually favored by another entity or group.
  • D. establishedPolicy
    Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
  • E. currentPolicy chosen
    Indicates that a given policy is the one presently in effect or actively governing the relevant context.
  • 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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f7308a096081909d66a56f3c926806 completed May 3, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69f72a00c5f081908b6539d15baf4e12 completed May 3, 2026, 10:57 a.m.
Created at: April 28, 2026, 4:29 a.m.