Triple
T24469952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFSP |
E617070
|
entity |
| Predicate | votingRuleException |
P23137
|
FINISHED |
| Object | qualified majority voting in specific CFSP cases |
—
|
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: qualified majority voting in specific CFSP cases | Statement: [CFSP, votingRuleException, qualified majority voting in specific CFSP cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingRuleException Context triple: [CFSP, votingRuleException, qualified majority voting in specific CFSP cases]
-
A.
presidingOfficerVoteException
Indicates an exception to the usual voting rules that allows the presiding officer to cast a vote under specific circumstances.
-
B.
reasonForVeto
Indicates the specific justification or grounds given for issuing a veto.
-
C.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
D.
votingRestriction
chosen
Indicates that there is a rule or limitation affecting who can vote, how they can vote, or under what conditions voting is allowed.
-
E.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299422cdc8190bc8d56243b7bc313 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.