Triple
T2426525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Sneferu at Dahshur |
E53540
|
entity |
| Predicate | necropolisRole |
P39127
|
FINISHED |
| Object | northernmost pyramid at Dahshur |
—
|
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: northernmost pyramid at Dahshur | Statement: [Pyramid of Sneferu at Dahshur, necropolisRole, northernmost pyramid at Dahshur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: necropolisRole Context triple: [Pyramid of Sneferu at Dahshur, necropolisRole, northernmost pyramid at Dahshur]
-
A.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
B.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
C.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
D.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
E.
majorMortuaryComplex
Indicates a significant funerary or burial-related architectural complex that serves as a primary site for mortuary activities.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc73d2e48190b6ad5f3ee75b74eb |
completed | March 7, 2026, 6:57 a.m. |
Created at: March 6, 2026, 9:42 p.m.