Triple

T31056413
Position Surface form Disambiguated ID Type / Status
Subject Drug Treatment and Testing Order E791409 entity
Predicate sanctionFor P39509 FINISHED
Object criminal offences 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: criminal offences | Statement: [Drug Treatment and Testing Order, sanctionFor, criminal offences]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sanctionFor
Context triple: [Drug Treatment and Testing Order, sanctionFor, criminal offences]
  • A. sanction chosen
    Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
  • B. coSanctionedBy
    Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
  • C. sanctionedAs
    Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
  • D. coSanctionedWith
    Indicates that an entity is subject to sanctions together with another entity, typically as part of the same sanctioning action or regime.
  • E. isSanctionedBy
    Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
  • 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_69f224cb08908190ba71ad9aa87518ed completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6a0ea04888190ac3a813b603bcb5c completed May 3, 2026, 1:12 a.m.
PD Predicate disambiguation batch_69f69fe463248190aa78128abeab1183 completed May 3, 2026, 1:07 a.m.
Created at: April 29, 2026, 9 p.m.