Triple
T13366573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalabsha |
E318952
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Osiris |
E8472
|
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: Osiris | Statement: [Kalabsha, hasDeity, Osiris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Osiris Context triple: [Kalabsha, hasDeity, Osiris]
-
A.
Osiris
chosen
Osiris is the ancient Egyptian god of the afterlife, resurrection, and fertility, often depicted as a mummified king and central to Egyptian funerary religion.
-
B.
Ptah
Ptah is an important ancient Egyptian creator god and patron of craftsmen and architects, especially revered as the chief deity of Memphis.
-
C.
Horus
Horus is a major ancient Egyptian sky and kingship god, often depicted as a falcon or falcon-headed man and closely associated with divine rulership and protection.
-
D.
Ptah-Tatenen
Ptah-Tatenen is an ancient Egyptian creator god who embodies the primeval mound and the fertile, life-giving earth, often worshipped as a composite form of Ptah and the chthonic deity Tatenen.
-
E.
Khonsu
Khonsu is an ancient Egyptian lunar god associated with time, healing, and protection, often worshipped as the son of Amun and Mut.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f754718a388190b4b85151a4694435 |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:32 p.m.