Triple
T29347938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebmaatre |
E744220
|
entity |
| Predicate | associatedWithRoyalEpithets |
P175311
|
FINISHED |
| Object | Beloved of Amun |
E1100423
|
NE 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: Beloved of Amun | Statement: [Nebmaatre, associatedWithRoyalEpithets, Beloved of Amun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoyalEpithets Context triple: [Nebmaatre, associatedWithRoyalEpithets, Beloved of Amun]
-
A.
hasRoyalEpithets
chosen
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
B.
associatedWithMonarch
Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
-
C.
associatedWithEpithet
Indicates that an entity is linked to or described by a particular epithet or descriptive label.
-
D.
royalNomen
Indicates that an entity bears a royal name or official titulary associated with monarchy or sovereign status.
-
E.
associatedWithMonarchy
Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
- F. None of above.
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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25a885a8e48190939cdd6f2f169493 |
completed | June 7, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: April 28, 2026, 2:03 p.m.