Triple
T14481132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usermaatre Setepenre |
E359102
|
entity |
| Predicate | royalFunction |
P114369
|
FINISHED |
| Object | legitimization of kingship |
—
|
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: legitimization of kingship | Statement: [Usermaatre Setepenre, royalFunction, legitimization of kingship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalFunction Context triple: [Usermaatre Setepenre, royalFunction, legitimization of kingship]
-
A.
royalDuties
Indicates that an entity has responsibilities, obligations, or functions associated with a royal role or position.
-
B.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
C.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
D.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
-
E.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.