Triple
T29418697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenhotep I |
E746096
|
entity |
| Predicate | mummyCurrentLocation |
P107967
|
FINISHED |
| Object | Egyptian Museum, Cairo |
—
|
NE NERFINISHED |
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: Egyptian Museum, Cairo | Statement: [Amenhotep I, mummyCurrentLocation, Egyptian Museum, Cairo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mummyCurrentLocation Context triple: [Amenhotep I, mummyCurrentLocation, Egyptian Museum, Cairo]
-
A.
mummyCurrentlyHousedAt
chosen
Indicates that a particular mummy is presently located or kept at a specified place or institution.
-
B.
mummyStatus
Indicates the condition or state of an entity specifically in relation to being a mummy (e.g., mummified, partially preserved, or not a mummy).
-
C.
mummyDiscovery
Indicates the event or relationship in which a mummy is found or brought to light, typically through archaeological or exploratory activity.
-
D.
mummyIdentified
Indicates that the identity of a mummy has been determined or confirmed.
-
E.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
- F. None of above.
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_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_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:03 p.m.