Triple
T33406088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anting, China |
E855441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automotive manufacturing hub |
C4810
|
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: automotive manufacturing hub Context triple: [Anting, China, instanceOf, automotive manufacturing hub]
-
A.
automotive manufacturing network
An automotive manufacturing network is an interconnected system of facilities, suppliers, logistics providers, and assembly plants that collaboratively design, produce, and deliver vehicles and components across regions or globally.
-
B.
automobile factory
An automobile factory is a large-scale industrial facility where raw materials and components are systematically assembled, tested, and finished into complete motor vehicles using coordinated machinery, labor, and production processes.
-
C.
automobile body manufacturer
An automobile body manufacturer is a company that designs, fabricates, and assembles the structural and exterior body components of vehicles for automakers.
-
D.
automotive factory
chosen
An automotive factory is a large-scale industrial facility where vehicles and their components are systematically designed, manufactured, assembled, and tested using specialized machinery, robotics, and human labor.
-
E.
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.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.