Triple
T32038775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus R (British Museum 10499) |
E818165
|
entity |
| Predicate | genreOfTextContained |
P22130
|
FINISHED |
| Object | ancient Egyptian literature |
—
|
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: ancient Egyptian literature | Statement: [Papyrus R (British Museum 10499), genreOfTextContained, ancient Egyptian literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfTextContained Context triple: [Papyrus R (British Museum 10499), genreOfTextContained, ancient Egyptian literature]
-
A.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
B.
literaryGenreOfWorkAppearedIn
Indicates the literary genre of the work in which a given entity (such as a text, character, or element) appears.
-
C.
literaryGenreAssociated
Indicates that there is an association between an entity and a particular literary genre with which it is related or classified.
-
D.
literaryGenreOfSourceWork
Indicates that a work belongs to, or is characterized by, a particular literary genre.
-
E.
genreDocumented
Indicates that a work’s genre has been formally recorded or documented.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:19 a.m.