Triple
T10646599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Bicolor |
E250849
|
entity |
| Predicate | kitDesignFeature |
P57584
|
FINISHED |
| Object | diagonal blue sash on white shirt |
—
|
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: diagonal blue sash on white shirt | Statement: [La Bicolor, kitDesignFeature, diagonal blue sash on white shirt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kitDesignFeature Context triple: [La Bicolor, kitDesignFeature, diagonal blue sash on white shirt]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
-
C.
ribbonDesignFeature
Indicates a design-related characteristic or attribute that is specifically associated with a ribbon.
-
D.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe1cd6081909df9e4dc0fda1f0b |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:05 p.m.