Triple
T6219591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Mugabe |
E139075
|
entity |
| Predicate | tookOfficeAsPrimeMinister |
P370
|
FINISHED |
| Object | 1980-04-18 |
—
|
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: 1980-04-18 | Statement: [Robert Mugabe, tookOfficeAsPrimeMinister, 1980-04-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOfficeAsPrimeMinister Context triple: [Robert Mugabe, tookOfficeAsPrimeMinister, 1980-04-18]
-
A.
heldOfficeOfPrimeMinisterThrough
Indicates that an entity continuously occupied and exercised the role and responsibilities of Prime Minister throughout a specified time period.
-
B.
officeHeldAsPrimeMinister
Indicates that an individual holds or has held the specific office or position of Prime Minister.
-
C.
primeMinisterAtStart
Indicates that the subject was serving as prime minister at the beginning of a specified period or event.
-
D.
primeMinisterTermStart
chosen
Indicates the date on which an individual officially begins serving as prime minister.
-
E.
primeMinisterAtEnactment
Indicates that the referenced person was serving as prime minister at the time a particular law, act, or measure was enacted.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bbb768819099402d367f124639 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.