Triple
T389257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mostafa Madbouly |
E8845
|
entity |
| Predicate | tookOfficeAsPrimeMinisterOfEgyptOn |
P370
|
FINISHED |
| Object | 2018-06-14 |
—
|
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: 2018-06-14 | Statement: [Mostafa Madbouly, tookOfficeAsPrimeMinisterOfEgyptOn, 2018-06-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOfficeAsPrimeMinisterOfEgyptOn Context triple: [Mostafa Madbouly, tookOfficeAsPrimeMinisterOfEgyptOn, 2018-06-14]
-
A.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
B.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
C.
inauguratedBy
Indicates that an official event, institution, or position was formally opened, initiated, or brought into operation by a specific person or authority.
-
D.
succeededByPrimeMinister
Indicates that one prime minister directly follows another in office as their immediate successor.
-
E.
primeMinisterTermStart
chosen
Indicates the date on which an individual officially begins serving as prime minister.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5bdc848190826701590070497b |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.