Triple
T29271965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | She Who Sees Horus and Seth |
E742142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian honorific title |
C19508
|
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 honorific title Context triple: [She Who Sees Horus and Seth, instanceOf, ancient Egyptian honorific title]
-
A.
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.
-
B.
ancient Egyptian royal epithet
chosen
An ancient Egyptian royal epithet is a formal, often symbolic title or phrase used to characterize and glorify a pharaoh’s divine status, political authority, and personal attributes in inscriptions and official contexts.
-
C.
Nubian title
A Nubian title is an honorific or official designation used in ancient Nubian societies to denote social rank, political authority, religious office, or royal status within their hierarchical structure.
-
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.
Arabic honorific title
An Arabic honorific title is a formal designation or epithet used to convey respect, status, religious standing, or lineage for an individual within Arabic-speaking and Islamic cultural contexts.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:48 p.m.