Triple
T14481119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usermaatre Setepenre |
E359102
|
entity |
| Predicate | positionInRoyalTitulary |
P78578
|
FINISHED |
| Object | throne 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 | Statement: [Usermaatre Setepenre, positionInRoyalTitulary, throne name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRoyalTitulary Context triple: [Usermaatre Setepenre, positionInRoyalTitulary, throne name]
-
A.
positionInRoyalFamily
Indicates the familial rank or role an individual holds within a royal family hierarchy.
-
B.
positionInRegalia
Indicates the specific role or rank an individual holds within a formal regalia or ceremonial order.
-
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.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
E.
titularyPosition
Indicates that one entity holds a formal or ceremonial title or position in relation to another entity.
- 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_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. |
Created at: April 10, 2026, 1:20 a.m.