Triple
T32038773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus R (British Museum 10499) |
E818165
|
entity |
| Predicate | mainWorkContained |
P173399
|
FINISHED |
| Object | The 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: The Tale of Sinuhe | Statement: [Papyrus R (British Museum 10499), mainWorkContained, The Tale of Sinuhe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkContained Context triple: [Papyrus R (British Museum 10499), mainWorkContained, The Tale of Sinuhe]
-
A.
mainWorkStatus
Indicates the current primary state or condition of a work (such as active, completed, pending, or inactive) within a given process or system.
-
B.
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.
-
C.
mainWorkSite
Indicates the primary location or site where an entity mainly performs its work or operations.
-
D.
isContainedInWorkBy
chosen
Indicates that something is included within, or forms a part of, a larger work created by a specified agent.
-
E.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
- 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_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:19 a.m.