Triple

T9493422
Position Surface form Disambiguated ID Type / Status
Subject Acts of the Parliament of Australia E228945 entity
Predicate mayAuthorize P13901 FINISHED
Object delegated legislation 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: delegated legislation | Statement: [Acts of the Parliament of Australia, mayAuthorize, delegated legislation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayAuthorize
Context triple: [Acts of the Parliament of Australia, mayAuthorize, delegated legislation]
  • A. canAuthorize chosen
    Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
  • B. mayGrant
    Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
  • C. mayPass
    Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
  • D. mayRuleOver
    Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
  • E. mayActThrough
    Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
  • 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_69ca847424f081908180305555139f7a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd95e8c8908190950e1130f9612823 completed April 1, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69cca5651a588190a3cfebe249a223e5 completed April 1, 2026, 4:56 a.m.
Created at: March 30, 2026, 7:56 p.m.