Triple
T24480142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khnem-ib-re |
E617348
|
entity |
| Predicate | bearsRoyalTitle |
P17683
|
FINISHED |
| Object | nesu-bit (King of Upper and Lower Egypt) |
—
|
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: nesu-bit (King of Upper and Lower Egypt) | Statement: [Khnem-ib-re, bearsRoyalTitle, nesu-bit (King of Upper and Lower Egypt)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearsRoyalTitle Context triple: [Khnem-ib-re, bearsRoyalTitle, nesu-bit (King of Upper and Lower Egypt)]
-
A.
isRoyalTitle
chosen
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
C.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
D.
kingConsortOfTitle
Indicates that a male monarch holds the position of king consort corresponding to a specific noble or royal title.
-
E.
crownedAs
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed509c88190a0071f8e78b38887 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.