Triple
T34727786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khui |
E1001118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian nobleman |
C12919
|
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 nobleman Context triple: [Khui, instanceOf, ancient Egyptian nobleman]
-
A.
ancient Egyptian official
chosen
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.
-
B.
ancient Egyptian noblewoman
An ancient Egyptian noblewoman is a high-status female member of Egyptian society, often connected to the royal court, who wielded social, economic, and religious influence through lineage, marriage, and estate management.
-
C.
Egyptian royal
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.
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.
-
E.
Person of the Sixth Dynasty of Egypt
A Person of the Sixth Dynasty of Egypt is an individual who lived under the rule of the Sixth Dynasty pharaohs (c. 2345–2181 BCE), participating in the political, social, religious, or economic life of Old Kingdom Egypt during its final phase.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.