Triple
T32127083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papyrus Berlin 3023 |
E820529
|
entity |
| Predicate | museumID |
P16930
|
FINISHED |
| Object | Berlin 3023 |
—
|
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: Berlin 3023 | Statement: [Papyrus Berlin 3023, museumID, Berlin 3023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumID Context triple: [Papyrus Berlin 3023, museumID, Berlin 3023]
-
A.
museumInventoryNumber
chosen
Indicates the unique catalog or inventory identifier assigned to an item within a museum’s collection.
-
B.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
C.
museumHolds
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
D.
museumOrSite
Indicates that one entity is a museum or cultural/historical site associated with or relevant to another entity.
-
E.
associatedWithMuseum
Indicates a relationship where an entity has a formal or recognized connection to a museum, such as ownership, curation, exhibition, or institutional affiliation.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b96c2f0881908d14683ecfe1af4b |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.