Triple
T27265441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkare |
E687887
|
entity |
| Predicate | linkedRulerPredecessor |
P80614
|
FINISHED |
| Object | Nefaarud I |
E1679525
|
NE 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: Nefaarud I | Statement: [Kheperkare, linkedRulerPredecessor, Nefaarud I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerPredecessor Context triple: [Kheperkare, linkedRulerPredecessor, Nefaarud I]
-
A.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
B.
predecessorRelations
Indicates that one entity comes before another in an ordered sequence or lineage, serving as its predecessor.
-
C.
usedByPredecessorOf
Indicates that something is used by an entity that is the predecessor of another entity in a sequence or hierarchy.
-
D.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
E.
contributedToPredecessorOf
Indicates that one entity contributed to or influenced another entity that came before a specified successor in a sequence or lineage.
- F. None of above.
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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12628966388190b8a992b91f3183d4 |
completed | May 24, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 10:55 a.m.