Triple
T34986606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Ankhesenpepi I |
E1008965
|
entity |
| Predicate | hasSpouseOfOwner |
P33561
|
FINISHED |
| Object | Pepi I Meryre |
—
|
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: Pepi I Meryre | Statement: [Pyramid of Ankhesenpepi I, hasSpouseOfOwner, Pepi I Meryre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseOfOwner Context triple: [Pyramid of Ankhesenpepi I, hasSpouseOfOwner, Pepi I Meryre]
-
A.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
B.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
-
C.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
D.
granteeSpouse
Indicates that one person is the spouse of the person who receives a grant, transfer, or similar benefit.
-
E.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:01 p.m.