Triple
T24283188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Council of the Armed Forces (Egypt) |
E605597
|
entity |
| Predicate | assumedPowerDate |
P12797
|
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: [Supreme Council of the Armed Forces (Egypt), assumedPowerDate, 2011-02-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedPowerDate Context triple: [Supreme Council of the Armed Forces (Egypt), assumedPowerDate, 2011-02-11]
-
A.
lostPowerDate
Indicates the date on which an entity lost electrical power or ceased to have power available.
-
B.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
C.
inPowerSince
chosen
Indicates the point in time from which an entity has continuously held a position of authority or power.
-
D.
appliedDate
Indicates the date on which an application or request was submitted or made.
-
E.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f53a8448190b66f6a97544bacc1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.