Triple
T33806616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sehetepibre |
E866408
|
entity |
| Predicate | followedByThroneName |
P87900
|
FINISHED |
| Object | Kheperkara |
—
|
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: Kheperkara | Statement: [Sehetepibre, followedByThroneName, Kheperkara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByThroneName Context triple: [Sehetepibre, followedByThroneName, Kheperkara]
-
A.
relatedThrone
Indicates a relationship in which an entity is connected or associated with a throne, typically through possession, claim, succession, or authority over it.
-
B.
throneName
Indicates the official royal or regnal name adopted by a ruler when they ascend to the throne.
-
C.
tookThroneFollowing
chosen
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
-
D.
linkedToThroneOf
Indicates a relationship where an entity is connected or related to a specific throne, typically through authority, succession, or symbolic association.
-
E.
throneStatus
Indicates the current state or condition of an entity’s claim to, or occupancy of, a throne or ruling 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 1, 2026, 1:46 a.m.