Triple
T33624527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahotep |
E861365
|
entity |
| Predicate | hasRoyalTitularyElement |
P78578
|
FINISHED |
| Object | Horus name |
—
|
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: Horus name | Statement: [Rahotep, hasRoyalTitularyElement, Horus name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalTitularyElement Context triple: [Rahotep, hasRoyalTitularyElement, Horus name]
-
A.
hasRoyalTitleType
Indicates that an entity holds a royal title of a specified type (e.g., king, queen, prince).
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
D.
hasRoyalEpithets
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
E.
hasRoyalNameElement
Indicates that an entity’s name includes a component that is associated with royalty or a royal title.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:41 a.m.