Triple

T32038917
Position Surface form Disambiguated ID Type / Status
Subject Papyrus Butler E818168 entity
Predicate relatedWork P37 FINISHED
Object Papyrus Berlin 3025
Papyrus Berlin 3025 is an ancient Egyptian manuscript housed in the Egyptian Museum of Berlin, notable for preserving literary and religious texts from the Middle Kingdom.
E1994251 NE 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: Papyrus Berlin 3025 | Statement: [Papyrus Butler, relatedWork, Papyrus Berlin 3025]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Papyrus Berlin 3025
Triple: [Papyrus Butler, relatedWork, Papyrus Berlin 3025]
Generated description
Papyrus Berlin 3025 is an ancient Egyptian manuscript housed in the Egyptian Museum of Berlin, notable for preserving literary and religious texts from the Middle Kingdom.

Provenance (5 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_69f6b49e063c819080287830c83f4207 completed May 3, 2026, 2:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f011366d4819084ab67602a667ab0 completed June 14, 2026, 7:29 p.m.
NEDg Description generation batch_6a2f04e7d7448190aaccfaa1b2f9cea5 completed June 14, 2026, 7:45 p.m.
NED2 Entity disambiguation (via description) batch_6a2f05aba10c81909afc967048decf07 completed June 14, 2026, 7:48 p.m.
Created at: May 1, 2026, 12:19 a.m.