Triple
T32719375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobekkare |
E836625
|
entity |
| Predicate | hasNameBearerRole |
P197529
|
FINISHED |
| Object | last ruler of the Twelfth Dynasty of Egypt |
—
|
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: last ruler of the Twelfth Dynasty of Egypt | Statement: [Sobekkare, hasNameBearerRole, last ruler of the Twelfth Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameBearerRole Context triple: [Sobekkare, hasNameBearerRole, last ruler of the Twelfth Dynasty of Egypt]
-
A.
hasGivenNameOfBearer
Indicates that a bearer (such as a person or entity) has a specific given (first) name.
-
B.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
C.
hasBearerFullName
Indicates that an entity (the bearer) is associated with a complete personal name string.
-
D.
hasRoleInName
Indicates that an entity’s role or function is explicitly reflected or encoded within its name.
-
E.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69fe991abc6c81908edbb98d61c9ca73 |
completed | May 9, 2026, 2:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.