Triple
T33085341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menmaatre |
E846622
|
entity |
| Predicate | successorPharaoh |
P45012
|
FINISHED |
| Object | Ramesses II |
—
|
NE NERFINISHED |
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: Ramesses II | Statement: [Menmaatre, successorPharaoh, Ramesses II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPharaoh Context triple: [Menmaatre, successorPharaoh, Ramesses II]
-
A.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
B.
successorAsHighPriestOfAmun
Indicates that one individual directly followed another in holding the position of High Priest of Amun.
-
C.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
D.
successorDynastyDeFacto
Indicates that one dynasty effectively functioned as the successor to another in practice, regardless of formal or legally recognized succession.
-
E.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:26 a.m.