Triple

T17468323
Position Surface form Disambiguated ID Type / Status
Subject Nekheb E425335 entity
Predicate hasAlternativeName P39 FINISHED
Object Elkab NE NERFINISHED

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: Elkab | Statement: [Nekheb, hasAlternativeName, Elkab]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elkab
Context triple: [Nekheb, hasAlternativeName, Elkab]
  • A. Elkab chosen
    Elkab is an ancient Egyptian city and archaeological site in Upper Egypt, notable as a major cult center of the vulture goddess Nekhbet.
  • B. Aswan
    Aswan is a historic city in southern Egypt on the Nile River, known for its ancient temples, quarries, and the nearby Aswan High Dam.
  • C. Kharga
    Kharga is a town in Egypt’s Western Desert that serves as the administrative center of the surrounding Kharga Oasis region.
  • D. Ain Sokhna
    Ain Sokhna is a popular Egyptian Red Sea resort town known for its beaches, proximity to Cairo, and role as a growing industrial and port area.
  • E. Qurna
    Qurna is a town in southern Iraq near the confluence of the Tigris and Euphrates rivers, historically significant as a strategic site during World War I.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451aa0e1c81909627369465575c06 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.