Triple
T33085288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sety I |
E846621
|
entity |
| Predicate | burialTemple |
P91865
|
FINISHED |
| Object | Mortuary temple at Qurna (Theban West Bank) |
—
|
NE NERFINISHED |
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: Mortuary temple at Qurna (Theban West Bank) | Statement: [Sety I, burialTemple, Mortuary temple at Qurna (Theban West Bank)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialTemple Context triple: [Sety I, burialTemple, Mortuary temple at Qurna (Theban West Bank)]
-
A.
burialPlaceIsShrine
Indicates that the place where someone is buried is a shrine, i.e., a site of religious or spiritual significance.
-
B.
hasMortuaryTemple
chosen
Indicates that a person, ruler, or deity is associated with or honored by a specific mortuary temple built for their funerary or commemorative purposes.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
E.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.