Triple
T32038806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khun-Anup |
E818166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian literary character |
C46263
|
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 literary character Context triple: [Khun-Anup, instanceOf, ancient Egyptian literary character]
-
A.
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.
-
B.
character in ancient Egyptian literature
chosen
A character in ancient Egyptian literature is an individual—human, divine, or supernatural—who participates in the narrative or didactic structure of texts such as myths, wisdom teachings, tales, and religious compositions, embodying cultural values, moral lessons, or cosmological roles.
-
C.
Theban hero
A Theban hero is a legendary figure from Greek mythology whose deeds, lineage, or fate are closely tied to the city of Thebes and its royal house.
-
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.
Theban warrior
A Theban warrior is a disciplined soldier from the ancient Greek city-state of Thebes, renowned for courage, tactical skill, and loyalty to their polis in both hoplite and elite military formations.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.