Triple
T17970882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamose |
E449335
|
entity |
| Predicate | mummyStatus |
P129953
|
FINISHED |
| Object | mummy discovered in Theban cache 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: mummy discovered in Theban cache DB320 | Statement: [Kamose, mummyStatus, mummy discovered in Theban cache DB320]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mummyStatus Context triple: [Kamose, mummyStatus, mummy discovered in Theban cache DB320]
-
A.
mummyCurrentlyHousedAt
Indicates that a particular mummy is presently located or kept at a specified place or institution.
-
B.
mortalStatus
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
C.
mysteryStatus
Indicates that an entity’s current state or condition is unknown, hidden, or intentionally left unexplained.
-
D.
mummyDiscoveryDate
Indicates the date on which a particular mummy was discovered.
-
E.
burialStatus
Indicates the state or condition of whether and how an entity has been buried.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fa67c48190936f20cea45e4599 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.