Triple
T29438719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Senate of Zimbabwe |
E746651
|
entity |
| Predicate | roleInChamber |
P88796
|
FINISHED |
| Object | presiding officer |
—
|
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: presiding officer | Statement: [President of the Senate of Zimbabwe, roleInChamber, presiding officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInChamber Context triple: [President of the Senate of Zimbabwe, roleInChamber, presiding officer]
-
A.
chamberRole
chosen
Indicates the specific function, position, or capacity an entity holds within a legislative or deliberative chamber.
-
B.
isChamber
Indicates that one entity functions as a chamber, room, or enclosed space in relation to another entity.
-
C.
roleInFirm
Indicates the specific position, function, or responsibility an entity holds within a firm or organization.
-
D.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
roleRelativeToOtherChamber
Indicates the functional or hierarchical position that one legislative chamber holds in relation to another chamber within the same governing body.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 28, 2026, 3:19 p.m.