Triple
T4217984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karnak Temple Complex |
E94267
|
entity |
| Predicate | primaryDeity |
P7648
|
FINISHED |
| Object | Amun-Re |
E73145
|
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: Amun-Re | Statement: [Karnak Temple Complex, primaryDeity, Amun-Re]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amun-Re Context triple: [Karnak Temple Complex, primaryDeity, Amun-Re]
-
A.
Amun
chosen
Amun is a major ancient Egyptian deity, often associated with the sun and creation and later merged with Ra as Amun-Ra, who became one of the chief gods of the Egyptian pantheon.
-
B.
Ra-Horakhty
Ra-Horakhty is an ancient Egyptian solar deity who combines aspects of the sun god Ra and the sky god Horus, often depicted as a falcon-headed man crowned with a solar disk.
-
C.
Khonsu
Khonsu is an ancient Egyptian lunar god associated with time, healing, and protection, often worshipped as the son of Amun and Mut.
-
D.
Atum
Atum is an ancient Egyptian creator god associated with the setting sun and the origin of the gods and the world.
-
E.
Ptah
Ptah is an important ancient Egyptian creator god and patron of craftsmen and architects, especially revered as the chief deity of Memphis.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b77294208190a53d6950dbf36351 |
completed | March 14, 2026, 7:30 p.m. |
Created at: March 12, 2026, 11:04 p.m.