Triple
T18430461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smenkhkare |
E450253
|
entity |
| Predicate | burialDebate |
P131575
|
FINISHED |
| Object | possibly KV55 in the Valley of the Kings |
—
|
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: possibly KV55 in the Valley of the Kings | Statement: [Smenkhkare, burialDebate, possibly KV55 in the Valley of the Kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialDebate Context triple: [Smenkhkare, burialDebate, possibly KV55 in the Valley of the Kings]
-
A.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
D.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
E.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b16b9c881908245c888a4b785bf |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:26 a.m.