Triple
T36558920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khahotepre Sobekhotep |
E901770
|
entity |
| Predicate | hasPersonalNameType |
P1081
|
FINISHED |
| Object | birth name |
—
|
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: birth name | Statement: [Khahotepre Sobekhotep, hasPersonalNameType, birth name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonalNameType Context triple: [Khahotepre Sobekhotep, hasPersonalNameType, birth name]
-
A.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
B.
isPersonalNameIn
Indicates that a personal name appears within or is contained in a specified context, such as a document, text span, or dataset.
-
C.
hasNoPersonalNameIn
Indicates that an entity lacks a specific personal name within a given context, language, or naming system.
-
D.
nameType
chosen
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
E.
hasGivenNames
Indicates that an entity possesses one or more personal (given) names assigned to it.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.