Triple
T38222310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lockstitch sewing machine |
E1012042
|
entity |
| Predicate | hasStitchStructure |
P138536
|
FINISHED |
| Object | interlocked top and bottom threads |
—
|
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: interlocked top and bottom threads | Statement: [lockstitch sewing machine, hasStitchStructure, interlocked top and bottom threads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStitchStructure Context triple: [lockstitch sewing machine, hasStitchStructure, interlocked top and bottom threads]
-
A.
stitchStructure
chosen
Indicates a relationship where one entity joins or binds parts of another entity together in a continuous, stitch-like structural manner.
-
B.
stitchTypeUsed
Indicates that a particular type of stitch is employed in performing or constructing the referenced action or object.
-
C.
producesStitch
Indicates that one entity creates or generates a stitch as a result of its action or function.
-
D.
numberOfStitches
Indicates the count of individual stitches involved in or required by an item, process, or event.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: May 3, 2026, 4:30 p.m.