Triple
T26425228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prints and Drawings Department |
E664351
|
entity |
| Predicate | focusesOnTechnique |
P31
|
FINISHED |
| Object | printmaking |
—
|
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: printmaking | Statement: [Prints and Drawings Department, focusesOnTechnique, printmaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnTechnique Context triple: [Prints and Drawings Department, focusesOnTechnique, printmaking]
-
A.
demonstratedTechniqueFocus
Indicates that an entity has shown or highlighted a particular technique as the main focus of its demonstration.
-
B.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
E.
techniqueRequired
Indicates that performing one entity (such as an action, process, or task) necessitates the use of a specific technique associated with the other entity.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 26, 2026, 11:45 p.m.