Triple
T378271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of Zimbabwe |
E8617
|
entity |
| Predicate | canOverrideSenateInSomeCases |
P10469
|
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 Zimbabwe, canOverrideSenateInSomeCases, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOverrideSenateInSomeCases Context triple: [National Assembly of Zimbabwe, canOverrideSenateInSomeCases, yes]
-
A.
canHoldSpecialSessions
Indicates that an entity has the authority or capability to convene special or extraordinary sessions outside the regular schedule.
-
B.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
-
C.
canAmendBills
Indicates that an entity has the authority or ability to modify, revise, or propose changes to bills.
-
D.
controlledByInSenate
Indicates that one political party or group holds the majority control or leadership over another entity within the context of the Senate.
-
E.
canImpeach
Indicates that one entity has the authority or power to formally impeach 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0be90881909e32d8fdb7aabb29 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.