Triple
T21648232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehytenweskhet I |
E534269
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Meryetneith |
—
|
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: Meryetneith | Statement: [Mehytenweskhet I, relative, Meryetneith]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Meryetneith Context triple: [Mehytenweskhet I, relative, Meryetneith]
-
A.
Meryetneith
chosen
Meryetneith was an ancient Egyptian royal woman, likely a queen or princess, known from the Late Period and associated with the powerful priestly and royal families of her time.
-
B.
Itaweret
Itaweret was an ancient Egyptian queen of the 12th Dynasty, known as the consort of Pharaoh Senusret II and likely the mother of his heir.
-
C.
Merneith
Merneith was an early First Dynasty Egyptian queen, likely a regent and possibly one of the first female rulers in recorded history.
-
D.
Merytre
Merytre was an ancient Egyptian queenly name borne by several royal women, most notably associated with the 18th Dynasty.
-
E.
Pentaweret
Pentaweret was an ancient Egyptian prince, likely a son of Pharaoh Ramesses III, who is believed to have been involved in the harem conspiracy against his father.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59124e1c81908d454894d66359e7 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 16, 2026, 6:35 p.m.