Triple
T17615502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thutmose I |
E429071
|
entity |
| Predicate | usedBurialInnovation |
P128294
|
FINISHED |
| Object | separate tomb and mortuary temple pattern |
—
|
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: separate tomb and mortuary temple pattern | Statement: [Thutmose I, usedBurialInnovation, separate tomb and mortuary temple pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBurialInnovation Context triple: [Thutmose I, usedBurialInnovation, separate tomb and mortuary temple pattern]
-
A.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
B.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
-
E.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3174008190a2b5bb1b061ea4df |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.