Triple
T521692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of France |
E10829
|
entity |
| Predicate | canCensureGovernment |
P2449
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Assembly of France, canCensureGovernment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCensureGovernment Context triple: [National Assembly of France, canCensureGovernment, yes]
-
A.
governmentAction
Indicates actions, decisions, or interventions carried out by a government or its agencies in relation to other entities.
-
B.
canImpeach
chosen
Indicates that one entity has the authority or power to formally impeach another entity.
-
C.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
D.
politicalRepercussion
Indicates that an action, event, or decision leads to consequences or fallout within a political context, such as shifts in power, public opinion, or policy.
-
E.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b372408190b3918fec45444674 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.