Triple
T38183315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanakht |
E1005234
|
entity |
| Predicate | predecessorHypothesis |
P97
|
FINISHED |
| Object | Khasekhemwy |
—
|
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: Khasekhemwy | Statement: [Sanakht, predecessorHypothesis, Khasekhemwy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorHypothesis Context triple: [Sanakht, predecessorHypothesis, Khasekhemwy]
-
A.
successorHypothesis
Indicates that one hypothesis directly follows and builds upon another in a sequence of related hypotheses.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorEstablished
Indicates that one entity was established before another, serving as its predecessor in origin or founding.
-
D.
predecessorGround
Indicates that one entity serves as the immediate prior version or state of another entity within a sequence or process.
-
E.
predecessorIsUncertain
Indicates that the identity or existence of the predecessor in a sequence or relationship is not known or cannot be determined with certainty.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:29 p.m.