Triple
T5916061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasperware pottery |
E131582
|
entity |
| Predicate | decorationStyle |
P60999
|
FINISHED |
| Object | neoclassical relief |
—
|
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: neoclassical relief | Statement: [Jasperware pottery, decorationStyle, neoclassical relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorationStyle Context triple: [Jasperware pottery, decorationStyle, neoclassical relief]
-
A.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
B.
decorationForm
chosen
Indicates the specific decorative style, pattern, or motif that characterizes how something is ornamented.
-
C.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
D.
decorationShape
Indicates the geometric or visual form that a decorative element or ornament takes in relation to the object it adorns.
-
E.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.