Triple
T36394058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobekhotep III |
E896411
|
entity |
| Predicate | burialPlaceHypothesis |
P65830
|
FINISHED |
| Object | unknown tomb, possibly in Abydos region |
—
|
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: unknown tomb, possibly in Abydos region | Statement: [Sobekhotep III, burialPlaceHypothesis, unknown tomb, possibly in Abydos region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialPlaceHypothesis Context triple: [Sobekhotep III, burialPlaceHypothesis, unknown tomb, possibly in Abydos region]
-
A.
possiblyBurialOf
chosen
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
-
B.
burialPlace
Indicates the location where a person or entity is buried.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
E.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.