Triple
T16509866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose II |
E401029
|
entity |
| Predicate | successorRoleOfHatshepsut |
P123827
|
FINISHED |
| Object | regent for Thutmose III |
—
|
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: regent for Thutmose III | Statement: [Thutmose II, successorRoleOfHatshepsut, regent for Thutmose III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorRoleOfHatshepsut Context triple: [Thutmose II, successorRoleOfHatshepsut, regent for Thutmose III]
-
A.
marriedToPharaoh
Indicates that one entity is the spouse of a pharaoh in a marital relationship.
-
B.
successorAsHighPriestOfAmun
Indicates that one individual directly followed another in holding the position of High Priest of Amun.
-
C.
predecessorAsGreatRoyalWife
Indicates that one entity previously held the role of Great Royal Wife immediately before the other entity.
-
D.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
E.
successorAsQueenMother
Indicates that one individual assumed the role of Queen Mother directly after another individual, succeeding her in that specific position.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54f7508190804bbae4c9bc8fe3 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.