Triple
T2499167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahure |
E52420
|
entity |
| Predicate | mortuaryTempleLocation |
P40157
|
FINISHED |
| Object | east side of his pyramid at Abusir |
—
|
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: east side of his pyramid at Abusir | Statement: [Sahure, mortuaryTempleLocation, east side of his pyramid at Abusir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mortuaryTempleLocation Context triple: [Sahure, mortuaryTempleLocation, east side of his pyramid at Abusir]
-
A.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
B.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
C.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
D.
majorMortuaryComplex
Indicates a significant funerary or burial-related architectural complex that serves as a primary site for mortuary activities.
-
E.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1afd86c81909181c4b45d4f8bc5 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:46 p.m.