Triple
T11282272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decora fashion |
E267092
|
entity |
| Predicate | typicalAccessoryMaterial |
P1272
|
FINISHED |
| Object | plastic |
—
|
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: plastic | Statement: [Decora fashion, typicalAccessoryMaterial, plastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAccessoryMaterial Context triple: [Decora fashion, typicalAccessoryMaterial, plastic]
-
A.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
typicalSoleMaterial
Indicates the material that is most commonly or characteristically used for the sole of an item, such as footwear.
-
D.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
-
E.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.