Triple
T28192489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nike Zoom Freak series |
E716353
|
entity |
| Predicate | hasColorways |
P14111
|
FINISHED |
| Object | Milwaukee Bucks-inspired colorways |
—
|
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: Milwaukee Bucks-inspired colorways | Statement: [Nike Zoom Freak series, hasColorways, Milwaukee Bucks-inspired colorways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorways Context triple: [Nike Zoom Freak series, hasColorways, Milwaukee Bucks-inspired colorways]
-
A.
colorVarietyOf
Indicates that one entity represents a specific color variant or color option of another entity.
-
B.
hasColorOption
chosen
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
C.
hasDiscColors
Indicates that an entity possesses one or more specified colors on its disc or disc-like component.
-
D.
stockColor
Indicates the color associated with a stock item or inventory product.
-
E.
hasDifferentDesignsFor
Indicates that one entity provides or uses multiple distinct designs tailored for different other entities or contexts.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: April 27, 2026, 10:26 p.m.