Triple

T22679912
Position Surface form Disambiguated ID Type / Status
Subject Apepi E560449 entity
Predicate opposedBy P437 FINISHED
Object Mehen 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: Mehen | Statement: [Apepi, opposedBy, Mehen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mehen
Context triple: [Apepi, opposedBy, Mehen]
  • A. Mehen chosen
    Mehen is an ancient Egyptian protective serpent deity who coils around the sun god Ra to shield him from threats like the chaos serpent Apep.
  • B. Thinis
    Thinis was an ancient Egyptian city traditionally regarded as the early dynastic capital and the center of the first pharaonic unification of Egypt.
  • C. Basti
    Basti is a common German diminutive form of the given name Sebastian.
  • D. Basti
    Basti is a city in the Indian state of Uttar Pradesh, known historically as part of the Purvanchal region and serving as an important local administrative and commercial center.
  • E. Merowe
    Merowe is a town in northern Sudan situated along the Nile River, known for its proximity to the Fourth Cataract and nearby archaeological and dam sites.
  • 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_69e2454bfd00819099115715a22cb057 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1785f68b4819082c5570f741f5135 completed April 29, 2026, 3:17 a.m.
Created at: April 17, 2026, 3:11 p.m.