Triple
T5836014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anuket |
E129470
|
entity |
| Predicate | consort |
P13
|
FINISHED |
| Object | Khnum |
E133265
|
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: Khnum | Statement: [Anuket, consort, Khnum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khnum Context triple: [Anuket, consort, Khnum]
-
A.
Khnum
chosen
Khnum is an ancient Egyptian ram-headed god associated with the Nile’s inundation, creation, and the molding of human beings on a potter’s wheel.
-
B.
Wepwawet
Wepwawet is an ancient Egyptian jackal-headed war and funerary god, often depicted as a path-opener who guided kings and the dead.
-
C.
Amun-her-khepeshef
Amun-her-khepeshef was a crown prince of ancient Egypt’s 19th Dynasty and the eldest son and heir apparent of Pharaoh Ramesses II.
-
D.
Sekhemti
Sekhemti is the ancient Egyptian Double Crown symbolizing the unified rule over Upper and Lower Egypt.
-
E.
Sobek
Sobek is an ancient Egyptian crocodile-headed god associated with the Nile, military power, and protection.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c034a358708190bfce78e7bd75db36 |
completed | March 22, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0bfce88f88190bbc78ce9c7c3c107 |
completed | March 23, 2026, 4:21 a.m. |
Created at: March 22, 2026, 3:54 p.m.