Triple
T24473821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quimper faience |
E617172
|
entity |
| Predicate | decorationMethod |
P30720
|
FINISHED |
| Object | freehand brushwork over glaze |
—
|
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: freehand brushwork over glaze | Statement: [Quimper faience, decorationMethod, freehand brushwork over glaze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorationMethod Context triple: [Quimper faience, decorationMethod, freehand brushwork over glaze]
-
A.
decorationClass
Indicates that one entity serves as a decorative classification or style category applied to another entity.
-
B.
decorationStart
Indicates the point in time or position at which a decoration or decorative process begins.
-
C.
decorationContext
Indicates the situational or environmental setting in which a decoration is used, applied, or intended to be perceived.
-
D.
decorationClassWithin
Indicates that one decoration class is spatially or logically contained within another decoration class.
-
E.
decorationSystem
chosen
Indicates a system or method used to apply, manage, or organize decorative elements in or around an 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299457ce081909e8d95fd482928dc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.