Triple

T38096212
Position Surface form Disambiguated ID Type / Status
Subject Ani E951249 entity
Predicate instanceOf P0 FINISHED
Object ancient Egyptian scribe 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 scribe
Context triple: [Ani, instanceOf, ancient Egyptian scribe]
  • A. 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.
  • 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. Egyptologist
    An Egyptologist is a scholar who specializes in the study of ancient Egypt’s history, language, culture, and archaeology through the analysis of texts, artifacts, and monuments.
  • D. 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.
  • E. ancient Alexandrian scholar
    An ancient Alexandrian scholar is a learned individual from the Hellenistic city of Alexandria who engages in the study, preservation, and critical analysis of knowledge across disciplines such as philosophy, mathematics, literature, and science within institutions like the Library and Museum of Alexandria.
  • 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_69f76f04960c8190a83f14ae4c67f5bc completed May 3, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:21 p.m.