Triple
T20057005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunéville embroidery |
E499363
|
entity |
| Predicate | sequinApplicationMethod |
P138537
|
FINISHED |
| Object | sequins applied with hook from underside |
—
|
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: sequins applied with hook from underside | Statement: [Lunéville embroidery, sequinApplicationMethod, sequins applied with hook from underside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequinApplicationMethod Context triple: [Lunéville embroidery, sequinApplicationMethod, sequins applied with hook from underside]
-
A.
stitchTypeUsed
Indicates that a particular type of stitch is employed in performing or constructing the referenced action or object.
-
B.
wearingMethod
Indicates the manner or method by which something is worn or put on.
-
C.
adornedWith
Indicates that one entity is decorated, embellished, or ornamented by another entity.
-
D.
stainMethod
Indicates the technique or procedure used to apply a stain to a material or specimen.
-
E.
ornamentationStyle
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
- F. None of above. chosen
Provenance (4 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663337d0c8190b82422802396cd67 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:38 p.m.