Triple
T12001772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teti |
E285681
|
entity |
| Predicate | praenomen |
P7966
|
FINISHED |
| Object | Seheteptawy |
E959328
|
NE 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: Seheteptawy | Statement: [Teti, praenomen, Seheteptawy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seheteptawy Context triple: [Teti, praenomen, Seheteptawy]
-
A.
Seheteptawy
chosen
Seheteptawy is the throne name of the ancient Egyptian pharaoh Teti, the first ruler of the Sixth Dynasty of the Old Kingdom.
-
B.
Sekhemre
Sekhemre was an ancient Egyptian royal figure, likely a prince or king associated with the lineage of Pharaoh Menkaura of the Fourth Dynasty.
-
C.
Merkheperre
Merkheperre was a relatively obscure pharaoh of ancient Egypt’s Second Intermediate Period, ruling during the later part of the 13th Dynasty.
-
D.
Nebhepetre
Nebhepetre was the throne name of Mentuhotep II, the Eleventh Dynasty pharaoh who reunified Egypt and initiated the Middle Kingdom.
-
E.
Nebethetepet
Nebethetepet is an ancient Egyptian goddess associated with Atum, often linked to concepts of satisfaction, offerings, and the manifestation of divine will.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c36b248190b446b17def94885b |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49d259f7c81908366e7d9e61a6c73 |
completed | May 1, 2026, 12:31 p.m. |
Created at: April 8, 2026, 9:46 p.m.