Triple

T9633141
Position Surface form Disambiguated ID Type / Status
Subject Legislative Council E232853 entity
Predicate typicalPower P89369 FINISHED
Object to make regulations subject to governor’s assent 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: to make regulations subject to governor’s assent | Statement: [Legislative Council, typicalPower, to make regulations subject to governor’s assent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalPower
Context triple: [Legislative Council, typicalPower, to make regulations subject to governor’s assent]
  • A. intendedPower
    Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
  • B. typicalEnergyRange
    Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
  • C. realPower
    Indicates that an entity possesses genuine, effective control or influence over another entity or situation, beyond nominal or formal authority.
  • D. powerRange
    Indicates the range of power values within which an entity operates, applies, or is considered valid.
  • E. primaryPower
    Indicates that one entity serves as the main or dominant source of power or energy for another entity.
  • 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_69ca848940cc8190b97cec654cb3bb4a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b28ce2c819086d3c6e4e6ea95a7 completed April 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69ccd5acfa5c8190aaba3cf548723604 completed April 1, 2026, 8:22 a.m.
PDg Predicate description generation batch_69ccd93fc45c8190a823305e461e581d completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:11 p.m.