Triple

T5301645
Position Surface form Disambiguated ID Type / Status
Subject royal veto of Louis XVI E119995 entity
Predicate vetoScope P63918 FINISHED
Object legislative decrees of the National Assembly 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 decrees of the National Assembly | Statement: [royal veto of Louis XVI, vetoScope, legislative decrees of the National Assembly]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vetoScope
Context triple: [royal veto of Louis XVI, vetoScope, legislative decrees of the National Assembly]
  • A. vetoType
    Indicates the specific kind or category of veto applied in a decision-making or approval process.
  • B. vetoedBy
    Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
  • C. vetoOverridden
    Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
  • D. vetoOverrideBy
    Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
  • E. cannotVeto
    Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by 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_69bd44704be88190acdb2ac481b0ff55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8e44e7c881909b241b2fec366038 completed March 20, 2026, 6:13 p.m.
PD Predicate disambiguation batch_69bd845097ac81909678624c4907fda4 completed March 20, 2026, 5:30 p.m.
PDg Predicate description generation batch_69bd8e43c4c88190bb72b9bf56c99425 completed March 20, 2026, 6:13 p.m.
Created at: March 20, 2026, 1:53 p.m.