Triple
T378250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of Zimbabwe |
E8617
|
entity |
| Predicate | canIntroduce |
P10468
|
FINISHED |
| Object | bills |
—
|
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: bills | Statement: [National Assembly of Zimbabwe, canIntroduce, bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canIntroduce Context triple: [National Assembly of Zimbabwe, canIntroduce, bills]
-
A.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
B.
introducedTo
Indicates that one entity caused or facilitated a first meeting or formal presentation between another entity and a third party.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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.