Triple
T5765104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nꜥr-mr |
E127191
|
entity |
| Predicate | nameBearerTitle |
P34139
|
FINISHED |
| Object | King of Upper and Lower 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: King of Upper and Lower Egypt | Statement: [nꜥr-mr, nameBearerTitle, King of Upper and Lower Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearerTitle Context triple: [nꜥr-mr, nameBearerTitle, King of Upper and Lower Egypt]
-
A.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
B.
titleHolderName
chosen
Indicates the name of the person or entity that holds a particular title or position.
-
C.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
D.
titleHeldByFamily
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
-
E.
laterTitleOfPatron
Indicates that one title held by a patron chronologically succeeds another title previously held by the same patron.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.