Triple
T8387807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Council of Ministers |
E197863
|
entity |
| Predicate | canBeBroughtDownBy |
P2359
|
FINISHED |
| Object | motion of no confidence |
—
|
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: motion of no confidence | Statement: [Federal Council of Ministers, canBeBroughtDownBy, motion of no confidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBroughtDownBy Context triple: [Federal Council of Ministers, canBeBroughtDownBy, motion of no confidence]
-
A.
canBeRemovedBy
chosen
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
B.
canBeDissectedBy
Indicates that one entity is capable of being divided or analyzed into parts by another entity or method.
-
C.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
D.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
E.
canLeadTo
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81076eac8190893813628cacc1aa |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.