Triple
T6363539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Council (Germany) |
E143169
|
entity |
| Predicate | typeOfVeto |
P16002
|
FINISHED |
| Object | suspensive veto on many laws |
—
|
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: suspensive veto on many laws | Statement: [Federal Council (Germany), typeOfVeto, suspensive veto on many laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVeto Context triple: [Federal Council (Germany), typeOfVeto, suspensive veto on many laws]
-
A.
vetoType
chosen
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.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
E.
vetoScope
Indicates that one party has the authority to reject or block certain decisions, actions, or proposals within a defined domain or set of matters.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.