Triple
T33585483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | associatedWithRoyalTitleOfBearer |
P17683
|
FINISHED |
| Object | King of Upper and Lower Egypt Senusret I |
E242783
|
NE 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: King of Upper and Lower Egypt Senusret I | Statement: [Kheperkara, associatedWithRoyalTitleOfBearer, King of Upper and Lower Egypt Senusret I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoyalTitleOfBearer Context triple: [Kheperkara, associatedWithRoyalTitleOfBearer, King of Upper and Lower Egypt Senusret I]
-
A.
hasRoyalTitleType
Indicates that an entity holds a royal title of a specified type (e.g., king, queen, prince).
-
B.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
pairedInRoyalTitleWith
Indicates that two individuals are jointly named or associated together within the same royal title (e.g., as co-rulers, consorts, or title partners).
-
D.
isRoyalTitle
chosen
Indicates that something is a formal title associated with royalty or a royal rank.
-
E.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
- F. None of above.
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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35afe75bfc819089cb09fd93c683d6 |
completed | June 19, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.