Triple
T17615477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose I |
E429071
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Mutnofret |
—
|
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: Mutnofret | Statement: [Thutmose I, spouse, Mutnofret]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mutnofret Context triple: [Thutmose I, spouse, Mutnofret]
-
A.
Mutnofret
chosen
Mutnofret was an ancient Egyptian queen of the early 18th Dynasty, likely a royal wife of Thutmose I and mother of Pharaoh Thutmose II.
-
B.
Weneg-Nebty
Weneg-Nebty was an obscure and possibly short-reigning pharaoh of Egypt’s Second Dynasty, known mainly from a few fragmentary inscriptions and debated identifications in early dynastic king lists.
-
C.
Hordjedef
Hordjedef was an ancient Egyptian prince of the 4th Dynasty, known from Old Kingdom texts as a royal son and a sage associated with wisdom literature.
-
D.
Merytre
Merytre was an ancient Egyptian queenly name borne by several royal women, most notably associated with the 18th Dynasty.
-
E.
Wepwawet
Wepwawet is an ancient Egyptian jackal-headed war and funerary god, often depicted as a path-opener who guided kings and the dead.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3174008190a2b5bb1b061ea4df |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 5:51 a.m.