Triple
T33585496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | usedInFuneraryContextOfBearer |
P196993
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kheperkara, usedInFuneraryContextOfBearer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFuneraryContextOfBearer Context triple: [Kheperkara, usedInFuneraryContextOfBearer, yes]
-
A.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
B.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
C.
hasPartInGrave
Indicates that an entity includes another entity as a physical component or element within a grave.
-
D.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
E.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
| PDg | Predicate description generation | batch_69fe72db8810819089e397961b8ead7a |
completed | May 8, 2026, 11:33 p.m. |
Created at: May 1, 2026, 1:40 a.m.