Triple
T8989411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebmaatre (attributed in some sources) |
E214750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian royal name |
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 name Context triple: [Nebmaatre (attributed in some sources), instanceOf, ancient Egyptian royal name]
-
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
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.
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.
-
D.
Theban royal
A Theban royal is a member of the ruling dynasty of ancient Thebes, holding political, religious, and military authority within the city-state and its territories.
-
E.
Mesopotamian royal epithet
A Mesopotamian royal epithet is a formal, often formulaic honorific phrase used in inscriptions and texts to define, praise, and legitimize a king’s divine favor, authority, and achievements.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:04 p.m.