Triple
T33038370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebkaure Khety |
E845382
|
entity |
| Predicate | hasRoyalNameElement |
P195462
|
FINISHED |
| Object | Ra |
—
|
NE NERFINISHED |
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: Ra | Statement: [Nebkaure Khety, hasRoyalNameElement, Ra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalNameElement Context triple: [Nebkaure Khety, hasRoyalNameElement, Ra]
-
A.
hasRoyalTitleType
Indicates that an entity holds a royal title of a specified type (e.g., king, queen, prince).
-
B.
hasRoyalEpithets
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
C.
hasRoyalSymbol
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
D.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
E.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: May 1, 2026, 1:24 a.m.