Triple
T20315759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntley & Palmers biscuit tins |
E510374
|
entity |
| Predicate | designTechnique |
P14965
|
FINISHED |
| Object | multicolour lithography |
—
|
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: multicolour lithography | Statement: [Huntley & Palmers biscuit tins, designTechnique, multicolour lithography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designTechnique Context triple: [Huntley & Palmers biscuit tins, designTechnique, multicolour lithography]
-
A.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
D.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
E.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67787af188190bc32a3049c9c5b39 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.