Triple
T29363442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mentuhotep IV |
E744652
|
entity |
| Predicate | possibleEndOfReign |
P15555
|
FINISHED |
| Object | replaced by his vizier Amenemhat |
—
|
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: replaced by his vizier Amenemhat | Statement: [Mentuhotep IV, possibleEndOfReign, replaced by his vizier Amenemhat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleEndOfReign Context triple: [Mentuhotep IV, possibleEndOfReign, replaced by his vizier Amenemhat]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
endOfSecondReign
Indicates that a second period of rule or governance by an entity has concluded.
-
C.
possibleReignPeriod
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
-
D.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
E.
thirdHolderReignEnd
Indicates the date or point in time when the reign or tenure of the third holder of a title, office, or position comes to an end.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:20 p.m.