Triple
T29418696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenhotep I |
E746096
|
entity |
| Predicate | mummyDiscovery |
P167158
|
FINISHED |
| Object | found in royal cache at Deir el-Bahri (DB320) |
—
|
LITERAL 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: found in royal cache at Deir el-Bahri (DB320) | Statement: [Amenhotep I, mummyDiscovery, found in royal cache at Deir el-Bahri (DB320)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mummyDiscovery Context triple: [Amenhotep I, mummyDiscovery, found in royal cache at Deir el-Bahri (DB320)]
-
A.
mummyDiscoveryDate
Indicates the date on which a particular mummy was discovered.
-
B.
mummyIdentified
Indicates that the identity of a mummy has been determined or confirmed.
-
C.
mummyCurrentlyHousedAt
Indicates that a particular mummy is presently located or kept at a specified place or institution.
-
D.
tombDiscovered
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
E.
numberOfRoyalMummiesDisplayed
Indicates the quantity of royal mummies that are currently being exhibited or put on public display.
- F. None of above. chosen
Provenance (4 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a677f548190a696da12ab251cd8 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:03 p.m.