Triple
T309721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate of Zimbabwe |
E6377
|
entity |
| Predicate | canDelayLegislation |
P11356
|
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: [Senate of Zimbabwe, canDelayLegislation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDelayLegislation Context triple: [Senate of Zimbabwe, canDelayLegislation, yes]
-
A.
canDelayMostPublicBillsFor
Indicates that one entity has the authority or power to postpone or obstruct the progression of most public legislative bills affecting another entity.
-
B.
canDelayMoneyBillsFor
Indicates that one entity has the authority or ability to postpone or extend the payment deadline of money-related bills for another entity.
-
C.
hasLegislativeProcess
Indicates that there exists a specific legislative procedure or set of steps governing how laws or regulations are proposed, debated, and enacted for the related entity.
-
D.
canAmendBills
Indicates that an entity has the authority or ability to modify, revise, or propose changes to bills.
-
E.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea33ba688190b30d285cd7aa0d82 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93f38308190b4b480c951f1a1c3 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2af1388190b93235602ace679e |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.