Triple

T18041586
Position Surface form Disambiguated ID Type / Status
Subject Misuse of Drugs Act 1971 E431664 entity
Predicate providesDefence P129572 FINISHED
Object lawful authority 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: lawful authority | Statement: [Misuse of Drugs Act 1971, providesDefence, lawful authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providesDefence
Context triple: [Misuse of Drugs Act 1971, providesDefence, lawful authority]
  • A. canBeDefendedIn
    Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
  • B. defends
    Indicates that one entity protects or supports another entity against attack, criticism, or harm.
  • C. defenceBody
    Indicates a relationship where an entity serves as the official body or organization responsible for defense or military affairs of another entity (such as a country or jurisdiction).
  • D. defenceHandledBy
    Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
  • E. defensiveCapability
    Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
  • 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_69d8b906482481908183315b9ecf9994 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4bfee78048190b3fada0eb3d28c77 completed April 19, 2026, 11:43 a.m.
PD Predicate disambiguation batch_69e3f908da508190a088aa837ea5b7af completed April 18, 2026, 9:35 p.m.
PDg Predicate description generation batch_69e42d8eefa88190a700c7c1b4213e46 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:25 a.m.