Triple
T24255460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotepsekhemwy |
E603654
|
entity |
| Predicate | hasRegnalStatus |
P66246
|
FINISHED |
| Object | historically attested ruler |
—
|
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: historically attested ruler | Statement: [Hotepsekhemwy, hasRegnalStatus, historically attested ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegnalStatus Context triple: [Hotepsekhemwy, hasRegnalStatus, historically attested ruler]
-
A.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
B.
reignStatus
chosen
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
C.
legalStatusOfMonarch
Indicates the legal status or standing that a monarch holds within a given legal or constitutional framework.
-
D.
hasCanonicalCoronationStatus
Indicates that an entity has an officially recognized or standard status with respect to a coronation.
-
E.
royalPrenomenStatus
Indicates the formal status or role associated with a ruler’s royal prenomen (throne name) within a given context or system.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6284dc8190a357f15d95b0360a |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.