Triple
T22040406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhen |
E544621
|
entity |
| Predicate | hasSerekhName |
P146364
|
FINISHED |
| Object | Ka |
—
|
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: Ka | Statement: [Sekhen, hasSerekhName, Ka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSerekhName Context triple: [Sekhen, hasSerekhName, Ka]
-
A.
serekhContains
Indicates that a serekh symbol encloses or contains a specific element, such as a royal name or inscription.
-
B.
isAmongFirstToUseSerekh
Indicates that an entity is among the earliest known individuals or groups to employ a serekh (an early royal emblem) in association with their name or identity.
-
C.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
-
D.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
-
E.
hasNumberOfNamesInscribed
Indicates the quantity of distinct names that are inscribed on a given entity.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:25 p.m.