Triple
T19489279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakenranef |
E487603
|
entity |
| Predicate | deathMethodTradition |
P11798
|
FINISHED |
| Object | burned alive |
—
|
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: burned alive | Statement: [Bakenranef, deathMethodTradition, burned alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathMethodTradition Context triple: [Bakenranef, deathMethodTradition, burned alive]
-
A.
killedByInSomeTraditions
Indicates that, according to at least some traditions or accounts, one entity is said to have been killed by another entity.
-
B.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
-
C.
deathMethod
chosen
Indicates the specific way or means by which a death occurred.
-
D.
deathPractice
Indicates a relationship where an entity engages in practices, rituals, or preparations specifically related to death or dying.
-
E.
martyrdomMethod
Indicates the method or means by which an individual becomes a martyr (i.e., how the martyrdom is carried out).
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348ad4088190b530f47efca90165 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.