Triple
T24146213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkhaf I |
E598391
|
entity |
| Predicate | hasShafts |
P155012
|
FINISHED |
| Object | multiple burial shafts in mastaba G 7430-7440 |
—
|
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: multiple burial shafts in mastaba G 7430-7440 | Statement: [Minkhaf I, hasShafts, multiple burial shafts in mastaba G 7430-7440]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShafts Context triple: [Minkhaf I, hasShafts, multiple burial shafts in mastaba G 7430-7440]
-
A.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
-
B.
propulsionShafts
Indicates a relationship where shafts are used to transmit mechanical power for propulsion between components of a system.
-
C.
typicalShaftType
Indicates the usual or characteristic type of shaft associated with an entity or configuration.
-
D.
shaftArrangement
Indicates how one or more shafts are positioned, oriented, or configured relative to each other within a mechanical or structural system.
-
E.
axeShaftColor
Indicates the color attribute associated with the shaft (handle) of an axe.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00b00708190bcd1d0b855230378 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:29 p.m.