Triple
T32680977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemre Khutawy Sobekhotep |
E835582
|
entity |
| Predicate | hasPrenomen |
P70695
|
FINISHED |
| Object | Sekhemre Khutawy |
—
|
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: Sekhemre Khutawy | Statement: [Sekhemre Khutawy Sobekhotep, hasPrenomen, Sekhemre Khutawy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrenomen Context triple: [Sekhemre Khutawy Sobekhotep, hasPrenomen, Sekhemre Khutawy]
-
A.
prenomen
Indicates the personal name or primary given name by which an individual is identified.
-
B.
praenomenOrNomen
Indicates that the related name element functions either as a personal given name (praenomen) or as a family/clan name (nomen) within a naming system.
-
C.
isPraenomenOf
chosen
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
D.
praenomenStatus
Indicates the status or role associated with a person's praenomen (given name), such as whether it is official, alternative, uncertain, or otherwise qualified.
-
E.
memberHasPraenomen
Indicates that a member is associated with or bears a specific praenomen (personal given name).
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: May 1, 2026, 1:09 a.m.