Triple
T18430456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smenkhkare |
E450253
|
entity |
| Predicate | predecessorDebate |
P97
|
FINISHED |
| Object | possibly preceded by Akhenaten |
—
|
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 preceded by Akhenaten | Statement: [Smenkhkare, predecessorDebate, possibly preceded by Akhenaten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorDebate Context triple: [Smenkhkare, predecessorDebate, possibly preceded by Akhenaten]
-
A.
predecessorSpeech
Indicates that one speech event directly precedes another in sequence or order.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
D.
hasDebatedPerson
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
E.
predecessorCoalition
Indicates that one coalition directly preceded another coalition in a sequence or timeline.
- 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_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. |
Created at: April 10, 2026, 11:26 a.m.