Triple
T34075688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elections in Zimbabwe |
E873901
|
entity |
| Predicate | monitoredByAbbreviation |
P178405
|
FINISHED |
| Object | SADC |
—
|
NE NERFINISHED |
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: SADC | Statement: [Elections in Zimbabwe, monitoredByAbbreviation, SADC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoredByAbbreviation Context triple: [Elections in Zimbabwe, monitoredByAbbreviation, SADC]
-
A.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
B.
isMonitoredIn
Indicates that an entity is being observed, tracked, or supervised within a particular context, system, or environment.
-
C.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
D.
monitoredWithSupportFrom
Indicates that an entity is being monitored or observed with assistance, resources, or backing provided by another entity.
-
E.
enforcedByAbbreviation
Indicates that a rule, standard, or requirement is imposed or upheld through the use of a specific abbreviation.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:52 a.m.