Triple
T27538903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemkheperre |
E695176
|
entity |
| Predicate | royalNamePosition |
P78578
|
FINISHED |
| Object | throne name in the royal titulary |
—
|
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 in the royal titulary | Statement: [Sekhemkheperre, royalNamePosition, throne name in the royal titulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalNamePosition Context triple: [Sekhemkheperre, royalNamePosition, throne name in the royal titulary]
-
A.
positionInRoyalFamily
Indicates the familial rank or role an individual holds within a royal family hierarchy.
-
B.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
C.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
D.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
E.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 1:30 p.m.