Triple
T425257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB4 |
E8192
|
entity |
| Predicate | logoProgram |
P14759
|
FINISHED |
| Object | USB-IF certified logos indicating performance levels |
—
|
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: USB-IF certified logos indicating performance levels | Statement: [USB4, logoProgram, USB-IF certified logos indicating performance levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logoProgram Context triple: [USB4, logoProgram, USB-IF certified logos indicating performance levels]
-
A.
logoFeature
Indicates that an entity serves as a distinctive visual element or component within a logo.
-
B.
logoImage
Indicates the image that serves as the logo representing an entity.
-
C.
flagshipProgram
Indicates that a program is the primary, most prominent, or most important offering associated with an entity.
-
D.
logoDescription
Indicates a textual description that explains the appearance, style, or content of a logo.
-
E.
logoDerivedFrom
Indicates that one logo is created, adapted, or otherwise based on another logo as its source or inspiration.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.