Triple
T2600141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of the Dead |
E58320
|
entity |
| Predicate | functionInBurial |
P25159
|
FINISHED |
| Object | placed in 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: placed in tombs | Statement: [Book of the Dead, functionInBurial, placed in tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInBurial Context triple: [Book of the Dead, functionInBurial, placed in tombs]
-
A.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
B.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
C.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
D.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
E.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd457564c819080d8c8818c02545a |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.