Triple
T7225401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidency of the Arab Republic of Egypt |
E150365
|
entity |
| Predicate | currentOfficeholderStart |
P61436
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Presidency of the Arab Republic of Egypt, currentOfficeholderStart, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficeholderStart Context triple: [Presidency of the Arab Republic of Egypt, currentOfficeholderStart, 2014]
-
A.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
B.
currentSpeakerAssumedOffice
Indicates that the person who is currently serving as speaker has taken up or begun holding a particular office or position.
-
C.
currentIncumbentStartYear
chosen
Indicates the year in which the entity’s current incumbent began their tenure or term in that role.
-
D.
firstOfficeHolderStart
Indicates the date or time when the first person to hold a particular office or position began their term.
-
E.
officeHolderAsOf
Indicates that a person holds or held a specific office or position as of a particular date or point in time.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.