Triple
T32845271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemre |
E840081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian royal figure |
C18959
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Egyptian royal figure Context triple: [Sekhemre, instanceOf, ancient Egyptian royal figure]
-
A.
Egyptian royal
chosen
An Egyptian royal is a member of the ruling family in ancient Egypt, typically a pharaoh or close relative, who holds political, religious, and ceremonial authority within the kingdom’s hierarchical society.
-
B.
ancient Egyptian royal woman
An ancient Egyptian royal woman is a high-status female member of the pharaonic court—such as a queen, princess, or royal consort—who played key political, religious, and dynastic roles within the ruling family.
-
C.
ancient Egyptian person
An ancient Egyptian person is an individual who lived in the Nile Valley civilization of ancient Egypt, shaped by its social hierarchy, religious beliefs, agricultural economy, and distinctive cultural practices.
-
D.
ancient Egyptian official
An ancient Egyptian official was a government administrator or bureaucrat responsible for managing state affairs such as taxation, justice, temple estates, and regional governance under the authority of the pharaoh.
-
E.
ancient Egyptian royal title
An ancient Egyptian royal title is a formal designation used to identify and legitimize a pharaoh or member of the royal family, often reflecting divine authority, political power, and religious roles within the kingdom.
- F. None of above.
Provenance (1 batch)
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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.