Triple
T4402618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nice Classification |
E93651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trademark classification system |
C7799
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: trademark classification system Context triple: [Nice Classification, instanceOf, trademark classification system]
-
A.
goods classification system
chosen
A goods classification system is a structured framework for categorizing products based on shared characteristics, such as type, use, material, or regulatory requirements, to enable consistent identification, management, and analysis.
-
B.
corporate trademark
A corporate trademark is a legally protected symbol, name, logo, or design that uniquely identifies and distinguishes a company's goods or services from those of others in the marketplace.
-
C.
bibliographic classification
A bibliographic classification is a systematic scheme for organizing library and information resources into categories and subcategories to facilitate efficient retrieval and browsing.
-
D.
taxonomic system
A taxonomic system is an organized framework for classifying and naming entities—such as organisms, objects, or concepts—into hierarchical categories based on shared characteristics and relationships.
-
E.
plant classification system
A plant classification system is an organized framework that categorizes plants into hierarchical groups based on shared characteristics such as morphology, genetics, and evolutionary relationships.
- F. None of above.
Provenance (1 batch)
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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:28 p.m.