Triple
T6945569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amina Hanim |
E160789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Egyptian royal consort |
C3879
|
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: Egyptian royal consort Context triple: [Amina Hanim, instanceOf, Egyptian royal consort]
-
A.
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.
-
B.
royal consort
chosen
A royal consort is the spouse of a reigning monarch who holds a recognized position at court, often with ceremonial duties but typically without sovereign authority.
-
C.
Ottoman consort
An Ottoman consort was a woman in the Ottoman imperial harem who, as a wife or favored companion of the sultan, held varying degrees of social, political, and ceremonial influence within the court.
-
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.
Byzantine empress consort
A Byzantine empress consort was the wife of a reigning Byzantine emperor who held significant ceremonial, political, and sometimes religious influence at the imperial court, though her authority was formally derived from her marriage rather than direct rule.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:28 p.m.