Triple
T1403349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosni Mubarak |
E31634
|
entity |
| Predicate | resignationDate |
P6919
|
FINISHED |
| Object | 2011-02-11 |
—
|
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: 2011-02-11 | Statement: [Hosni Mubarak, resignationDate, 2011-02-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignationDate Context triple: [Hosni Mubarak, resignationDate, 2011-02-11]
-
A.
resignationDateOfRespondent
chosen
Indicates the date on which the respondent formally resigned from their position or role.
-
B.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
C.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
E.
relievedOnDate
Indicates that an entity was formally released, discharged, or relieved from a role, duty, or obligation on a specific date.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.