Triple
T37759622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khakaure |
E941222
|
entity |
| Predicate | linkedRulerBirthName |
P198801
|
FINISHED |
| Object | Senusret III |
—
|
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: Senusret III | Statement: [Khakaure, linkedRulerBirthName, Senusret III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerBirthName Context triple: [Khakaure, linkedRulerBirthName, Senusret III]
-
A.
notableMemberBirthName
Indicates the birth name of a notable member associated with an entity.
-
B.
creatorBirthName
Indicates the full birth name originally given to the creator of a work or entity.
-
C.
honoursPersonBirthName
Indicates that an entity formally recognizes or commemorates a person using the name they were given at birth.
-
D.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
E.
authorBirthName
Indicates the full personal name an author was given at birth, before any later name changes or pseudonyms.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69ff069ddf948190bdfe438953249dd0 |
completed | May 9, 2026, 10:04 a.m. |
Created at: May 3, 2026, 4:19 p.m.