Triple
T33585469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | predecessorThroneNameOfBearer |
P122590
|
FINISHED |
| Object | Sehetepibre |
—
|
NE NERFINISHED |
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: Sehetepibre | Statement: [Kheperkara, predecessorThroneNameOfBearer, Sehetepibre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorThroneNameOfBearer Context triple: [Kheperkara, predecessorThroneNameOfBearer, Sehetepibre]
-
A.
predecessorThroneName
chosen
Indicates that one throne name immediately preceded another in a succession or lineage of rulership.
-
B.
predecessorAsKing
Indicates that one entity previously held the position of king immediately before the other entity.
-
C.
predecessorAsHeirApparent
Indicates that one entity previously held the position of heir apparent to another entity (such as a throne, title, or office) before being succeeded in that role.
-
D.
predecessorAsDeFactoRuler
Indicates that one entity previously held actual ruling power over a domain or group, regardless of formal title, before another entity assumed that de facto control.
-
E.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:40 a.m.