Triple
T33228534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmose-Nefertari |
E850626
|
entity |
| Predicate | precededByAsGreatRoyalWife |
P119684
|
FINISHED |
| Object | Ahhotep I |
—
|
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: Ahhotep I | Statement: [Ahmose-Nefertari, precededByAsGreatRoyalWife, Ahhotep I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByAsGreatRoyalWife Context triple: [Ahmose-Nefertari, precededByAsGreatRoyalWife, Ahhotep I]
-
A.
predecessorAsGreatRoyalWife
chosen
Indicates that one entity previously held the role of Great Royal Wife immediately before the other entity.
-
B.
predecessorAsQueenConsort
Indicates that one queen consort held the position immediately before another queen consort in a royal succession.
-
C.
successorAsGreatRoyalWife
Indicates that one individual became the next holder of the position or role of Great Royal Wife after another individual.
-
D.
predecessorAsQueen
Indicates that one entity previously held the position of queen immediately before another entity.
-
E.
predecessorAsDuchessConsort
Indicates that one entity previously held the role of duchess consort immediately before another entity in a succession.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:30 a.m.