Triple
T10875501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatch Show Print |
E256787
|
entity |
| Predicate | usesPrintingTechnique |
P8374
|
FINISHED |
| Object | letterpress printing |
—
|
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: letterpress printing | Statement: [Hatch Show Print, usesPrintingTechnique, letterpress printing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrintingTechnique Context triple: [Hatch Show Print, usesPrintingTechnique, letterpress printing]
-
A.
usedPrintingPressAt
Indicates that one entity operated or made use of a printing press at, or in connection with, another entity (such as a place, time, or event).
-
B.
printingMethod
chosen
Indicates the technique or process used to produce a printed item or image.
-
C.
hasPrintFeature
Indicates that an entity possesses a specific printing-related characteristic or capability.
-
D.
overprints
Indicates that one entity is printed or superimposed on top of another, partially or completely covering the underlying material or pattern.
-
E.
printedInColor
Indicates that something was produced or reproduced using multiple ink colors rather than only black-and-white.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7518a1db08190abf0c524b81487fa |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.