Triple
T33585470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | successorThroneNameOfBearer |
P200689
|
FINISHED |
| Object | Khakheperre |
—
|
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: Khakheperre | Statement: [Kheperkara, successorThroneNameOfBearer, Khakheperre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorThroneNameOfBearer Context triple: [Kheperkara, successorThroneNameOfBearer, Khakheperre]
-
A.
predecessorThroneName
Indicates that one throne name immediately preceded another in a succession or lineage of rulership.
-
B.
successorDynasticClaimant
Indicates that one entity is the next recognized claimant to a dynastic title, throne, or inheritance following another entity.
-
C.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line of succession.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
| PDg | Predicate description generation | batch_69ffa15c3f348190a59403bc72ac9ed4 |
completed | May 9, 2026, 9:04 p.m. |
Created at: May 1, 2026, 1:40 a.m.