Triple
T30662829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKX |
E780577
|
entity |
| Predicate | hasUnderlyingCompanyBrandName |
P27763
|
FINISHED |
| Object | Skechers |
—
|
NE NERFINISHED |
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: Skechers | Statement: [SKX, hasUnderlyingCompanyBrandName, Skechers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingCompanyBrandName Context triple: [SKX, hasUnderlyingCompanyBrandName, Skechers]
-
A.
hasUnderlyingCompanyBrand
chosen
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
B.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
C.
hasUnderlyingCompanyFlagshipProduct
Indicates that a product is the primary or flagship offering of a given company.
-
D.
underlyingCompanyName
Indicates the name of the company that serves as the foundational or primary entity underlying another entity, structure, or instrument.
-
E.
containsComponentBrand
Indicates that an entity includes, as part of its composition or structure, a component produced or branded by a specified brand.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:31 p.m.