Triple
T16075741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tausret |
E389974
|
entity |
| Predicate | tombReuse |
P121800
|
FINISHED |
| Object | later usurped and extended by Setnakhte |
—
|
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: later usurped and extended by Setnakhte | Statement: [Tausret, tombReuse, later usurped and extended by Setnakhte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombReuse Context triple: [Tausret, tombReuse, later usurped and extended by Setnakhte]
-
A.
tombNumber
Indicates the specific identifying number assigned to a particular tomb within a set of tombs.
-
B.
tombOwnership
Indicates a relationship in which one entity holds legal or traditional ownership rights over a specific tomb.
-
C.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
D.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
-
E.
reburialCoincidesWith
Indicates that the act of reburial occurs at the same time or within the same event or phase as another specified occurrence.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:57 a.m.