Triple
T4433996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxor Temple |
E95602
|
entity |
| Predicate | dedicatedTo |
P500
|
FINISHED |
| Object | Amun |
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 | Statement: [Luxor Temple, dedicatedTo, Amun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amun Context triple: [Luxor Temple, dedicatedTo, Amun]
-
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.
Khonsu
Khonsu is an ancient Egyptian lunar god associated with time, healing, and protection, often worshipped as the son of Amun and Mut.
-
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.
Ptah
Ptah is an important ancient Egyptian creator god and patron of craftsmen and architects, especially revered as the chief deity of Memphis.
-
E.
Khnum
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.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35587bc048190aee8e0ed94b6e064 |
completed | March 13, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b67baa14648190811970a45dd0d185 |
completed | March 15, 2026, 9:28 a.m. |
Created at: March 12, 2026, 11:31 p.m.