Triple
T6993521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gütermann family |
E162142
|
entity |
| Predicate | productAssociation |
P62838
|
FINISHED |
| Object | sewing thread |
—
|
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: sewing thread | Statement: [Gütermann family, productAssociation, sewing thread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productAssociation Context triple: [Gütermann family, productAssociation, sewing thread]
-
A.
relatedToProduct
chosen
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
B.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
C.
associatedItemDescription
Indicates that there is a descriptive text or explanation specifically about an item that is linked or connected to another entity or context.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
productVariant
Indicates that one entity is a specific variant or version of a more general product 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.