Triple
T17970868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamose |
E449335
|
entity |
| Predicate | coregencyStatus |
P93700
|
FINISHED |
| Object | possibly co-regent with Seqenenre Tao |
—
|
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: possibly co-regent with Seqenenre Tao | Statement: [Kamose, coregencyStatus, possibly co-regent with Seqenenre Tao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coregencyStatus Context triple: [Kamose, coregencyStatus, possibly co-regent with Seqenenre Tao]
-
A.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
-
B.
coregencyClaim
chosen
Indicates a claim that two or more individuals jointly hold, or are entitled to hold, the same ruling or governing authority at the same time.
-
C.
collectiveStatus
Indicates the overall state or condition shared by a group of entities considered together as a collective.
-
D.
collectivityStatus
Indicates the state or condition of being part of a collective group versus being individual or separate.
-
E.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fa67c48190936f20cea45e4599 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.