Triple
T25853132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Automobile Trade Association |
E651268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automobile dealers association |
C50800
|
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: automobile dealers association Context triple: [Chicago Automobile Trade Association, instanceOf, automobile dealers association]
-
A.
automotive manufacturing alliance
An automotive manufacturing alliance is a collaborative partnership between multiple vehicle manufacturers and related industry stakeholders formed to share resources, technology, and expertise to improve efficiency, innovation, and competitiveness in producing automobiles.
-
B.
automotive retailer
An automotive retailer is a business that sells new and/or used vehicles, related financing, and support services directly to consumers.
-
C.
motor car dealership
A motor car dealership is a business that buys, sells, and services new or used motor vehicles, acting as an intermediary between manufacturers and customers.
-
D.
automotive industry agreement
An automotive industry agreement is a formal contract or arrangement between parties in the automotive sector that defines terms for collaboration, production, supply, standards, or other industry-related activities.
-
E.
automobile importer
An automobile importer is an entity or individual that purchases vehicles from foreign manufacturers or markets and arranges their transportation, customs clearance, and compliance with local regulations for sale or use in the destination country.
- F. None of above. chosen
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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:59 a.m.