Triple
T31311069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Report of Wenamun |
E798462
|
entity |
| Predicate | papyrusDesignation |
P171561
|
FINISHED |
| Object | Papyrus Moscow 120 |
—
|
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: Papyrus Moscow 120 | Statement: [The Report of Wenamun, papyrusDesignation, Papyrus Moscow 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: papyrusDesignation Context triple: [The Report of Wenamun, papyrusDesignation, Papyrus Moscow 120]
-
A.
pyramidDesignation
Indicates that one entity is formally designated or classified as a pyramid in relation to another entity or context.
-
B.
PyrgiTabletsMaterial
Indicates that something is made of, or composed from, the material used for the Pyrgi Tablets.
-
C.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
D.
parchmentColor
Indicates that one entity has the color characteristic of parchment in relation to another entity.
-
E.
EgyptianVersionInscribedOn
Indicates that an Egyptian-language version of a text or inscription is carved or written onto a particular physical object or surface.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:15 p.m.