Triple
T5813293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Unas |
E128921
|
entity |
| Predicate | hasBurialChamber |
P42823
|
FINISHED |
| Object | granite-lined burial chamber |
—
|
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: granite-lined burial chamber | Statement: [Pyramid of Unas, hasBurialChamber, granite-lined burial chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialChamber Context triple: [Pyramid of Unas, hasBurialChamber, granite-lined burial chamber]
-
A.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
B.
hasBurialVault
chosen
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
C.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
D.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
E.
chamberOfFinalPassage
Indicates a relationship where a location serves as the last or decisive venue through which something (such as legislation, a process, or a journey) must pass before completion or enactment.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b56044c8190847478a342d441c2 |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.