Triple
T20057003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunéville embroidery |
E499363
|
entity |
| Predicate | stitchStructure |
P138536
|
FINISHED |
| Object | chain stitch on underside of fabric |
—
|
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: chain stitch on underside of fabric | Statement: [Lunéville embroidery, stitchStructure, chain stitch on underside of fabric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stitchStructure Context triple: [Lunéville embroidery, stitchStructure, chain stitch on underside of fabric]
-
A.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
B.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
C.
spawnStructure
Indicates that an entity causes a new structure to be created or instantiated in the environment.
-
D.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
E.
producesStructure
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
- 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.