Triple
T7083424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Nyuserre Ini |
E165011
|
entity |
| Predicate | hasReliefDecorations |
P14580
|
FINISHED |
| Object | mortuary temple walls |
—
|
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: mortuary temple walls | Statement: [Pyramid of Nyuserre Ini, hasReliefDecorations, mortuary temple walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliefDecorations Context triple: [Pyramid of Nyuserre Ini, hasReliefDecorations, mortuary temple walls]
-
A.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
B.
hasRelief
chosen
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
C.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
D.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
E.
hasBackCarvings
Indicates that an entity possesses carvings or engraved markings specifically located on its back.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5102be08190bbde790bfa8fe9e2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.