Triple
T18549800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferneferure |
E453340
|
entity |
| Predicate | parentalReign |
P113744
|
FINISHED |
| Object | reign of Akhenaten |
—
|
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: reign of Akhenaten | Statement: [Neferneferure, parentalReign, reign of Akhenaten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalReign Context triple: [Neferneferure, parentalReign, reign of Akhenaten]
-
A.
fatherReign
chosen
Indicates that one entity’s period of ruling or governance occurs during, or is defined in relation to, the reign of its father.
-
B.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
C.
reignedUnder
Indicates that one entity exercised ruling authority or governance while being subordinate to, or under the higher sovereignty of, another entity.
-
D.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
E.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534beeb408190a03f6d7c3f2ef389 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.