Triple
T19209276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashubian embroidery |
E480314
|
entity |
| Predicate | typicalStitch |
P45780
|
FINISHED |
| Object | satin stitch |
—
|
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: satin stitch | Statement: [Kashubian embroidery, typicalStitch, satin stitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStitch Context triple: [Kashubian embroidery, typicalStitch, satin stitch]
-
A.
stitchTypeUsed
chosen
Indicates that a particular type of stitch is employed in performing or constructing the referenced action or object.
-
B.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
-
C.
typicalWeavingTechnique
Indicates that one entity is the characteristic or commonly used weaving method associated with another entity.
-
D.
typicalCostumePattern
Indicates that one entity is the characteristic or commonly used costume pattern associated with another entity.
-
E.
typicalWear
Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a000188190afb762ea24bc3deb |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:20 p.m.