Triple
T5896831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son of Ra |
E131120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian royal epithet |
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 royal epithet Context triple: [Son of Ra, instanceOf, ancient Egyptian royal epithet]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
local form of Horus
A local form of Horus is a regionally distinct manifestation of the Egyptian god Horus, adapted to specific cities or cult centers while retaining his core attributes of kingship and protection.
-
E.
Ancient Egyptian dynasty
An Ancient Egyptian dynasty is a succession of rulers from the same family or lineage who governed Egypt during a distinct historical period, often characterized by shared political, cultural, and religious developments.
- F. None of above. chosen
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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.