Triple
T11039239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemkhet |
E260964
|
entity |
| Predicate | coregencyOrSuccessionContext |
P97434
|
FINISHED |
| Object | early Old Kingdom |
—
|
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: early Old Kingdom | Statement: [Sekhemkhet, coregencyOrSuccessionContext, early Old Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coregencyOrSuccessionContext Context triple: [Sekhemkhet, coregencyOrSuccessionContext, early Old Kingdom]
-
A.
successionRelation
Indicates that one entity follows another in an ordered sequence, such as in time, position, or rank.
-
B.
successorPowerContext
Indicates that one entity holds or exercises power or authority as a successor within a particular contextual or situational framework.
-
C.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
D.
successorContext
Indicates that one context directly follows and continues from another in a sequence or process.
-
E.
typeOfSuccessionContext
Indicates the specific situational or legal framework within which a succession or transfer of authority, rights, or ownership takes place.
- F. None of above. chosen
Provenance (4 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fe93b081909d58bfd4b42715f0 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.