Triple
T23205579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu'l-Misk Kafur |
E580443
|
entity |
| Predicate | roseTo |
P46172
|
FINISHED |
| Object | political leadership in Egypt |
—
|
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: political leadership in Egypt | Statement: [Abu'l-Misk Kafur, roseTo, political leadership in Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseTo Context triple: [Abu'l-Misk Kafur, roseTo, political leadership in Egypt]
-
A.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
-
B.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
C.
rise
Indicates an upward movement, increase, or ascent of something relative to a previous or lower state.
-
D.
roseToPowerIn
chosen
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
E.
roseToPowerThrough
Indicates the means, process, or circumstances by which an entity gained authority, control, or a dominant position.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907c1d7c8190aca252a39ae0da86 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.