Triple
T16075707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ay |
E389973
|
entity |
| Predicate | successorLegitimacy |
P32191
|
FINISHED |
| Object | contested by Horemheb |
—
|
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: contested by Horemheb | Statement: [Ay, successorLegitimacy, contested by Horemheb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLegitimacy Context triple: [Ay, successorLegitimacy, contested by Horemheb]
-
A.
dynasticLegitimacyBasedOn
Indicates that the recognized legitimacy or right to rule of a dynasty is founded upon, justified by, or derived from a specified basis or source.
-
B.
governsSuccessionOf
Indicates that an entity establishes or controls the rules or process by which another entity’s position, title, or role is passed on to successors.
-
C.
governedSuccessionOf
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
-
D.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
E.
successionConflict
chosen
Indicates a dispute or struggle over who has the legitimate right to succeed to a position, title, or authority.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.