Triple

T7193805
Position Surface form Disambiguated ID Type / Status
Subject Presentment Clause E167759 entity
Predicate usedToInvalidate P53170 FINISHED
Object legislative veto mechanisms 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: legislative veto mechanisms | Statement: [Presentment Clause, usedToInvalidate, legislative veto mechanisms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedToInvalidate
Context triple: [Presentment Clause, usedToInvalidate, legislative veto mechanisms]
  • A. canInvalidate
    Indicates that one entity has the ability or authority to render another entity invalid, ineffective, or no longer in force.
  • B. invalidated
    Indicates that one entity has rendered another entity null, void, or no longer legally or logically effective.
  • C. usedToAbrogate chosen
    Indicates that something served as the means or instrument by which a rule, law, agreement, or obligation was annulled, repealed, or rendered no longer valid.
  • D. usedUntil
    Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
  • E. usedToAuthorize
    Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an 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_69c6888b5248819090499a884ee3ec39 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e9036544819083c70a5d2135ba4b completed March 27, 2026, 8:30 p.m.
PD Predicate disambiguation batch_69c6e752385c819096fbab55566ee2a8 completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:50 p.m.