Triple
T24667268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udimu |
E610714
|
entity |
| Predicate | hasRoyalNameType |
P7836
|
FINISHED |
| Object | Horus name |
—
|
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: Horus name | Statement: [Udimu, hasRoyalNameType, Horus name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalNameType Context triple: [Udimu, hasRoyalNameType, Horus name]
-
A.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
B.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
C.
hasCrownName
chosen
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
D.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
E.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:41 a.m.