Triple
T14272962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prints and Drawings Study Room |
E353837
|
entity |
| Predicate | mediaHandled |
P33573
|
FINISHED |
| Object | paper |
—
|
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: paper | Statement: [Prints and Drawings Study Room, mediaHandled, paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaHandled Context triple: [Prints and Drawings Study Room, mediaHandled, paper]
-
A.
mediaResponse
Indicates that one entity serves as a reply or reaction in a media format (such as audio, video, or image) to another entity or communication.
-
B.
mediaUse
chosen
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
C.
mediaCovered
Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
-
D.
mediaActivity
Indicates an action or engagement involving the creation, use, sharing, or interaction with media content.
-
E.
mediaMoment
Indicates a specific point or segment within a media item (such as a video, audio, or broadcast) where a notable event or action occurs.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de65811d7c8190b075909a6570d415 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.