Triple
T16075733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tausret |
E389974
|
entity |
| Predicate | roleDuringSiptahReign |
P43583
|
FINISHED |
| Object | regent |
—
|
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: regent | Statement: [Tausret, roleDuringSiptahReign, regent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringSiptahReign Context triple: [Tausret, roleDuringSiptahReign, regent]
-
A.
childMerneptahRole
Indicates that the subject is a child of Merneptah and specifies the role or position that child holds in relation to him.
-
B.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
C.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
D.
namedForRoleOfImhotep
Indicates that something is named after, or in reference to, the role or function historically associated with Imhotep.
-
E.
roleInMonarchyPeriod
chosen
Indicates that an entity held a specific role or position during a defined period of a monarchy.
- 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_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. |
Created at: April 10, 2026, 4:57 a.m.