Triple

T1085404
Position Surface form Disambiguated ID Type / Status
Subject Wadjet E24038 entity
Predicate associatedWith P37 FINISHED
Object Nekhbet E95465 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Nekhbet | Statement: [Wadjet, associatedWith, Nekhbet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nekhbet
Context triple: [Wadjet, associatedWith, Nekhbet]
  • A. Wadjet
    Wadjet is an ancient Egyptian cobra goddess associated with royal protection, kingship, and the land of Lower Egypt.
  • B. Hathor
    Hathor is an ancient Egyptian goddess associated with love, music, motherhood, fertility, and joy, often depicted as a cow or a woman with cow horns and a sun disk.
  • C. Sekhmet
    Sekhmet is an ancient Egyptian lioness-headed goddess associated with war, destruction, and healing, revered as a powerful protector and bringer of both plague and cure.
  • D. Neith
    Neith is an ancient Egyptian goddess associated with war, hunting, and weaving, often revered as a creator deity and protector of Lower Egypt.
  • E. vulture goddess Nekhbet chosen
    The vulture goddess Nekhbet is an ancient Egyptian protective deity of Upper Egypt, often depicted as a vulture spreading her wings over pharaohs as their guardian.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b961d0cc8190858296b44fab2f32 completed March 1, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac9971114c81909769b3ad78b95189 completed March 7, 2026, 9:32 p.m.
Created at: March 1, 2026, 7:42 p.m.