Triple
T33845502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Political Agreement |
E867467
|
entity |
| Predicate | createdOfficeFor |
P3709
|
FINISHED |
| Object | Morgan Tsvangirai |
—
|
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: Morgan Tsvangirai | Statement: [Global Political Agreement, createdOfficeFor, Morgan Tsvangirai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdOfficeFor Context triple: [Global Political Agreement, createdOfficeFor, Morgan Tsvangirai]
-
A.
officeCreatedFor
chosen
Indicates that an office or position was established specifically to serve, represent, or support a particular entity.
-
B.
allocatesOffice
Indicates assigning a specific office or workspace to an individual or organizational unit.
-
C.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
D.
officeCreatedAsResultOf
Indicates that an office came into existence as a consequence of a specific preceding event, action, or process.
-
E.
createdExecutivePower
Indicates that an entity is responsible for establishing or bringing into existence a particular executive authority or executive power structure.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:47 a.m.