Triple
T7654045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasekhemwy |
E173329
|
entity |
| Predicate | royalTitularyFeature |
P78578
|
FINISHED |
| Object | combined Horus and Seth names |
—
|
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: combined Horus and Seth names | Statement: [Khasekhemwy, royalTitularyFeature, combined Horus and Seth names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalTitularyFeature Context triple: [Khasekhemwy, royalTitularyFeature, combined Horus and Seth names]
-
A.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
styleOfMonarchTitle
Indicates the specific formal style or wording used in the official title of a monarch.
-
C.
representativeOfMonarchTitle
Indicates that one entity serves as the official representative or holder of authority on behalf of a monarch’s title.
-
D.
regentTitle
Indicates the official title held by a person serving as regent (i.e., governing on behalf of another, such as a monarch or minor).
-
E.
royalTitleConfirmed
Indicates that an individual's royal title has been formally validated or officially recognized.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7061b218c81909fff789ba4c10e58 |
completed | March 27, 2026, 10:35 p.m. |
Created at: March 27, 2026, 3:59 p.m.