Triple
T24695981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instruction of Hordjedef |
E611584
|
entity |
| Predicate | hasWorkTitleVariant |
P160063
|
FINISHED |
| Object | Instruction of Djedefhor |
—
|
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: Instruction of Djedefhor | Statement: [Instruction of Hordjedef, hasWorkTitleVariant, Instruction of Djedefhor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleVariant Context triple: [Instruction of Hordjedef, hasWorkTitleVariant, Instruction of Djedefhor]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
C.
hasWorkTitlePattern
Indicates that an entity’s work title follows or matches a specified pattern or structured format.
-
D.
hasWorkingTitleStatus
Indicates that an entity currently holds the status of having a provisional or working title rather than a finalized official title.
-
E.
workFromWhichTitleDerived
Indicates that a title is derived from, or based on, a particular underlying work.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 3:21 a.m.