Triple

T2368621
Position Surface form Disambiguated ID Type / Status
Subject Resource Management Act 1991 E46038 entity
Predicate hasBeenSubjectTo P1313 FINISHED
Object numerous amendments since 1991 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: numerous amendments since 1991 | Statement: [Resource Management Act 1991, hasBeenSubjectTo, numerous amendments since 1991]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBeenSubjectTo
Context triple: [Resource Management Act 1991, hasBeenSubjectTo, numerous amendments since 1991]
  • A. isSubjectTo chosen
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • B. hasBeenSubjectOf
    Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
  • C. hasNotableSubject
    Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
  • D. hasAct
    Indicates that an entity performs, participates in, or is associated with a specific act or action.
  • E. hasTypicalSubject
    Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
  • 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_69a88a145268819083e2736cb835c696 completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abc76bf75c8190b014c3dbfc46bba3 completed March 7, 2026, 6:36 a.m.
PD Predicate disambiguation batch_69abc59b88348190a2d6c08f69974117 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:56 p.m.