Triple
T26480132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenirdis I |
E664655
|
entity |
| Predicate | adoptedDaughter |
P130878
|
FINISHED |
| Object | Shepenupet II |
—
|
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: Shepenupet II | Statement: [Amenirdis I, adoptedDaughter, Shepenupet II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedDaughter Context triple: [Amenirdis I, adoptedDaughter, Shepenupet II]
-
A.
hasAdoptiveDaughter
chosen
Indicates that one person stands in an adoptive parent–child relationship specifically as the parent of a daughter.
-
B.
daughterOf
Indicates that one person is the female child (daughter) of another person.
-
C.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
D.
adoptedThrough
Indicates that an adoption relationship was established or carried out by means of a specified process, channel, or intermediary.
-
E.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fa3f4481908d1db59213f734d2 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:26 a.m.