Triple
T32038531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawit |
E818158
|
entity |
| Predicate | burialContainer |
P173797
|
FINISHED |
| Object | richly decorated sarcophagus |
—
|
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: richly decorated sarcophagus | Statement: [Kawit, burialContainer, richly decorated sarcophagus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialContainer Context triple: [Kawit, burialContainer, richly decorated sarcophagus]
-
A.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
B.
burialDetail
Indicates details about how, where, and under what circumstances an entity is buried.
-
C.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
-
D.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
E.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:19 a.m.