Triple
T29418711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenhotep I |
E746096
|
entity |
| Predicate | childrenStatus |
P167427
|
FINISHED |
| Object | no clearly attested surviving heir |
—
|
LITERAL FINISHED |
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: no clearly attested surviving heir | Statement: [Amenhotep I, childrenStatus, no clearly attested surviving heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childrenStatus Context triple: [Amenhotep I, childrenStatus, no clearly attested surviving heir]
-
A.
childStatus
Indicates the current condition, role, or state of a child entity in relation to its parent or context.
-
B.
childrenFounded
Indicates that the subject’s children established, created, or founded the object entity (such as an organization, institution, or project).
-
C.
childIs
Indicates that one entity is the child (offspring or subordinate descendant) of another entity.
-
D.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
-
E.
childrenReceive
Indicates that one or more children are the recipients of something (such as an item, benefit, or message) from another source.
- F. None of above. chosen
Provenance (4 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_69f66a677f548190a696da12ab251cd8 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 3:03 p.m.