Triple
T30298022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses XI |
E770572
|
entity |
| Predicate | contemporaryHighPriestOfAmun |
P115349
|
FINISHED |
| Object | Herihor |
—
|
NE NERFINISHED |
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: Herihor | Statement: [Ramesses XI, contemporaryHighPriestOfAmun, Herihor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryHighPriestOfAmun Context triple: [Ramesses XI, contemporaryHighPriestOfAmun, Herihor]
-
A.
successorAsHighPriestOfAmun
Indicates that one individual directly followed another in holding the position of High Priest of Amun.
-
B.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
C.
notablePriest
chosen
Indicates that the subject is recognized as a priest of particular significance or prominence in some context.
-
D.
ShemuIs
Indicates that one entity is identified as or classified as "Shemu" in relation to another entity or context.
-
E.
currentPatriarch
Indicates that one entity is the present, officially recognized patriarch (religious or familial head) of 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 7:48 p.m.