Triple
T10692089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenemhat III |
E252034
|
entity |
| Predicate | associatedWithDeity |
P1481
|
FINISHED |
| Object | Sobek |
E166500
|
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: Sobek | Statement: [Amenemhat III, associatedWithDeity, Sobek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sobek Context triple: [Amenemhat III, associatedWithDeity, Sobek]
-
A.
Sobek
chosen
Sobek is an ancient Egyptian crocodile-headed god associated with the Nile, military power, and protection.
-
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.
Khonsu
Khonsu is an ancient Egyptian lunar god associated with time, healing, and protection, often worshipped as the son of Amun and Mut.
-
D.
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.
-
E.
Amun
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.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd37cf408190a1912b3e0aa096a5 |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998cfeb748190bfff06534d83cf97 |
completed | April 11, 2026, 12:41 a.m. |
Created at: April 8, 2026, 9:11 p.m.