Triple
T35599380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nefer |
E1028725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian given name |
C18761
|
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 given name Context triple: [Nefer, instanceOf, ancient Egyptian given name]
-
A.
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.
-
B.
ancient Egyptian person
chosen
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.
-
C.
ancient Greek name
An ancient Greek name is a personal identifier originating from the language, mythology, history, and cultural practices of ancient Greece, often reflecting virtues, gods, heroes, or familial lineage.
-
D.
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.
-
E.
African given name
An African given name is a personal name bestowed at birth or a significant life event within an African cultural context, often reflecting language, heritage, values, circumstances of birth, or aspirations for the individual.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.