Triple
T16381149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siptah |
E397807
|
entity |
| Predicate | associatedWithTombDecorationStyle |
P123172
|
FINISHED |
| Object | late 19th Dynasty royal tombs |
—
|
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: late 19th Dynasty royal tombs | Statement: [Siptah, associatedWithTombDecorationStyle, late 19th Dynasty royal tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTombDecorationStyle Context triple: [Siptah, associatedWithTombDecorationStyle, late 19th Dynasty royal tombs]
-
A.
tombDecoration
Indicates that something serves as an ornamental or symbolic adornment associated with a tomb.
-
B.
associatedTomb
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
C.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
D.
cemeteryStyle
Indicates the stylistic or design characteristics that define how a cemetery is arranged or presented.
-
E.
tombDecorationPhase
Indicates the specific stage or phase in which decorative work was applied to a tomb.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319dd0e0c8190812bde6a2f7d9644 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.