Triple
T10055926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkaura |
E208860
|
entity |
| Predicate | successorDynastically |
P1551
|
FINISHED |
| Object | Fifth Dynasty of Egypt (indirectly) |
—
|
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: Fifth Dynasty of Egypt (indirectly) | Statement: [Menkaura, successorDynastically, Fifth Dynasty of Egypt (indirectly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastically Context triple: [Menkaura, successorDynastically, Fifth Dynasty of Egypt (indirectly)]
-
A.
successorDynasty
chosen
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
C.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
D.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
-
E.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfacacd08190abe66f8bb17b92c7 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.