Triple
T29418709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenhotep I |
E746096
|
entity |
| Predicate | spouseTraditionallyAttributed |
P24262
|
FINISHED |
| Object | Ahmose-Meritamon |
—
|
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: Ahmose-Meritamon | Statement: [Amenhotep I, spouseTraditionallyAttributed, Ahmose-Meritamon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseTraditionallyAttributed Context triple: [Amenhotep I, spouseTraditionallyAttributed, Ahmose-Meritamon]
-
A.
spouseTraditionNote
Indicates a note or comment describing traditional customs, practices, or contextual information related to a person’s spouse relationship.
-
B.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
C.
hasSpouseInTradition
chosen
Indicates that one entity is recognized as the spouse of another according to a specified cultural, religious, or legal tradition.
-
D.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
E.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 3:03 p.m.