Triple
T27332003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedjkheperre Setepenre |
E689826
|
entity |
| Predicate | royalNameCategory |
P78578
|
FINISHED |
| Object | throne name distinct from birth 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: throne name distinct from birth name | Statement: [Hedjkheperre Setepenre, royalNameCategory, throne name distinct from birth name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalNameCategory Context triple: [Hedjkheperre Setepenre, royalNameCategory, throne name distinct from birth name]
-
A.
namedForMonarch
Indicates that one entity bears a name derived from or given in honor of a monarch.
-
B.
royalNomen
Indicates that an entity bears a royal name or official titulary associated with monarchy or sovereign status.
-
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.
royalHouseNameForm
Indicates the specific linguistic or formal version of a royal house’s name used in a given context.
-
E.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:38 a.m.