Triple
T18430455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smenkhkare |
E450253
|
entity |
| Predicate | successorDebate |
P131574
|
FINISHED |
| Object | possibly succeeded by Tutankhamun |
—
|
LITERAL 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: possibly succeeded by Tutankhamun | Statement: [Smenkhkare, successorDebate, possibly succeeded by Tutankhamun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDebate Context triple: [Smenkhkare, successorDebate, possibly succeeded by Tutankhamun]
-
A.
majorDebateSeries
Indicates a relationship where an event or program is part of a prominent, recurring series of formal debates.
-
B.
successorSpeech
Indicates that one speech or spoken segment directly follows another in sequence, serving as its immediate successor.
-
C.
successorCampaign
Indicates that one campaign directly follows and continues or replaces another campaign in sequence.
-
D.
successorCompetition
Indicates that one competition directly follows another in sequence, serving as its successor in a series or timeline.
-
E.
successorFormation
Indicates that one entity comes into existence as the direct replacement or continuation of another, typically following the end or transformation of the predecessor.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b16b9c881908245c888a4b785bf |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:26 a.m.