Triple

T16853861
Position Surface form Disambiguated ID Type / Status
Subject vignette ads E409737 entity
Predicate policyRestriction P125239 FINISHED
Object must not block content permanently 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: must not block content permanently | Statement: [vignette ads, policyRestriction, must not block content permanently]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: policyRestriction
Context triple: [vignette ads, policyRestriction, must not block content permanently]
  • A. policyRequirement
    Indicates that one entity specifies a rule, condition, or obligation that another entity must satisfy according to a policy.
  • B. policyException
    Indicates that a specific case is exempted from or does not have to follow an otherwise applicable policy or rule.
  • C. politicalRestriction
    Indicates that there are limitations or prohibitions imposed on an entity’s political activities, rights, or participation.
  • D. policyImplication
    Indicates that one policy, decision, or condition leads to, justifies, or necessitates another policy outcome or course of action.
  • E. restrictionOfPact
    Indicates a relationship where one pact imposes limitations, conditions, or constraints on another pact or agreement.
  • 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b37bbb80819086d844a313625cad completed April 18, 2026, 4:38 p.m.
PD Predicate disambiguation batch_69e32b8cbb048190878a259cc5be960e completed April 18, 2026, 6:58 a.m.
PDg Predicate description generation batch_69e355722040819098830dabf207ecd6 completed April 18, 2026, 9:57 a.m.
Created at: April 10, 2026, 5:24 a.m.