Triple
T29347937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebmaatre |
E744220
|
entity |
| Predicate | pairedWithBirthName |
P80791
|
FINISHED |
| Object | Amenhotep (Heqawaset) |
—
|
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: Amenhotep (Heqawaset) | Statement: [Nebmaatre, pairedWithBirthName, Amenhotep (Heqawaset)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWithBirthName Context triple: [Nebmaatre, pairedWithBirthName, Amenhotep (Heqawaset)]
-
A.
bearerBirthNameOf
chosen
Indicates that one entity is the birth name originally given to and borne by another entity.
-
B.
spouseBirthName
Indicates the birth name of a person's spouse, prior to any name changes such as through marriage.
-
C.
appliesToPersonBirthName
Indicates that the referenced value is used as the birth name of the specified person.
-
D.
pairedNickname
Indicates that two entities share or are associated with a complementary or matching set of nicknames.
-
E.
pairedWithRelationshipName
Indicates that one entity is associated with another as a named pair within a specific relationship context.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669595a0881908ea97caf704fefb3 |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:03 p.m.