Triple
T24454181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemib |
E616631
|
entity |
| Predicate | titularyComponentOfType |
P91895
|
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: [Sekhemib, titularyComponentOfType, Horus name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titularyComponentOfType Context triple: [Sekhemib, titularyComponentOfType, Horus name]
-
A.
hasTitularyElement
chosen
Indicates that an entity includes or is associated with a specific titulary component, such as a formal title, epithet, or honorific element, as part of its designation.
-
B.
titularyPosition
Indicates that one entity holds a formal or ceremonial title or position in relation to another entity.
-
C.
typeOfTitleInheritance
Indicates the manner or rule by which a title is passed from one holder to another (e.g., hereditary, elective, or appointed succession).
-
D.
belongsToTitleSystem
Indicates that something is part of, or governed by, a particular title system or titling scheme.
-
E.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to another entity.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c4f1d881909d9119fec74afe53 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.