Triple
T34986634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Ankhesenpepi I |
E1008965
|
entity |
| Predicate | hasOwnerFatherInLaw |
P18081
|
FINISHED |
| Object | Teti |
—
|
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: Teti | Statement: [Pyramid of Ankhesenpepi I, hasOwnerFatherInLaw, Teti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnerFatherInLaw Context triple: [Pyramid of Ankhesenpepi I, hasOwnerFatherInLaw, Teti]
-
A.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
B.
possibleFatherInLaw
Indicates that one person is a potential or candidate father-in-law of another, typically as the (possible) father of that person’s spouse or prospective spouse.
-
C.
fatherInLaw
chosen
Indicates a relationship where one person is the father of another person's spouse or the spouse of someone's parent.
-
D.
fatherInLawInPlot
Indicates that one person is the father-in-law of another within the context of a specific plot or storyline.
-
E.
grandparentInLawOf
Indicates that one person is the grandparent of another person’s spouse, or the spouse of another person’s grandparent.
- 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_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.