Triple
T16509864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose II |
E401029
|
entity |
| Predicate | successorWasMinorAtDeath |
P16541
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thutmose II, successorWasMinorAtDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorWasMinorAtDeath Context triple: [Thutmose II, successorWasMinorAtDeath, true]
-
A.
successorAsMinorUnderRegencyOf
Indicates that one entity becomes the next ruler or officeholder while still a minor, with another entity serving as regent who governs on their behalf.
-
B.
cameToPowerAsMinor
chosen
Indicates that an individual assumed ruling authority or leadership while still legally or socially considered a minor.
-
C.
predecessorAsHeirApparent
Indicates that one entity previously held the position of heir apparent to another entity (such as a throne, title, or office) before being succeeded in that role.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
hasLineOfSuccession
Indicates that one entity is designated to follow or replace another in a defined order of succession.
- 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_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. |
Created at: April 10, 2026, 5:14 a.m.