Triple
T32038733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Papyrus 3022 |
E818164
|
entity |
| Predicate | mainWorkPreserved |
P21692
|
FINISHED |
| Object | Tale of Sinuhe |
—
|
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: Tale of Sinuhe | Statement: [Berlin Papyrus 3022, mainWorkPreserved, Tale of Sinuhe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkPreserved Context triple: [Berlin Papyrus 3022, mainWorkPreserved, Tale of Sinuhe]
-
A.
mainWorkPeriod
Indicates the primary or most significant span of time during which an entity is active, employed, or engaged in a particular work or role.
-
B.
mainWorkStatus
Indicates the current primary state or condition of a work (such as active, completed, pending, or inactive) within a given process or system.
-
C.
mainWorkSite
Indicates the primary location or site where an entity mainly performs its work or operations.
-
D.
workPreservedIn
chosen
Indicates that a work is maintained, stored, or archived within a particular medium, collection, or repository so that it remains accessible over time.
-
E.
mainWorkCommentedOn
Indicates that a commentary, review, or critical work is focused on and discusses a particular primary work.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49cf8d4819096d6beb7e880b821 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:19 a.m.