Triple
T33085328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menmaatre |
E846622
|
entity |
| Predicate | belongsToRoyalTitulary |
P78578
|
FINISHED |
| Object | Fivefold titulary of the pharaoh |
—
|
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: Fivefold titulary of the pharaoh | Statement: [Menmaatre, belongsToRoyalTitulary, Fivefold titulary of the pharaoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRoyalTitulary Context triple: [Menmaatre, belongsToRoyalTitulary, Fivefold titulary of the pharaoh]
-
A.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
B.
hasRoyalTitleType
Indicates that an entity holds a royal title of a specified type (e.g., king, queen, prince).
-
C.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
D.
hasRoyalEpithets
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
E.
associatedTitleOfSovereign
Indicates a formal title that is linked to or held by a particular sovereign.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 1, 2026, 1:26 a.m.