Triple
T32038483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashayet |
E818156
|
entity |
| Predicate | hasTombDecoration |
P116514
|
FINISHED |
| Object | painted reliefs |
—
|
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: painted reliefs | Statement: [Ashayet, hasTombDecoration, painted reliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTombDecoration Context triple: [Ashayet, hasTombDecoration, painted reliefs]
-
A.
tombDecoration
chosen
Indicates that something serves as an ornamental or symbolic adornment associated with a tomb.
-
B.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
C.
hasTombChapel
Indicates that an entity possesses or is associated with a specific tomb chapel as part of its funerary or commemorative context.
-
D.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
E.
associatedWithTombDecorationStyle
Indicates a relationship where something is linked to, characterized by, or connected with a particular style of tomb decoration.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:19 a.m.