Triple
T10876528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwean general election, 2013 |
E256812
|
entity |
| Predicate | AUAssessment |
P45603
|
FINISHED |
| Object | generally peaceful but with concerns |
—
|
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: generally peaceful but with concerns | Statement: [Zimbabwean general election, 2013, AUAssessment, generally peaceful but with concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AUAssessment Context triple: [Zimbabwean general election, 2013, AUAssessment, generally peaceful but with concerns]
-
A.
assessment
chosen
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
B.
assessedBy
Indicates that an entity has been evaluated, examined, or judged by another entity (typically an agent or authority).
-
C.
assessmentName
Indicates the specific title or label assigned to an assessment within a system or context.
-
D.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
E.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ac901881909938cabe4d21bdbf |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.