Triple
T24801042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangzhou, China (GAC FCA, earlier production) |
E620522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint-venture manufacturing facility |
C17544
|
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: joint-venture manufacturing facility Context triple: [Guangzhou, China (GAC FCA, earlier production), instanceOf, joint-venture manufacturing facility]
-
A.
manufacturing plant
A manufacturing plant is a large-scale industrial facility where raw materials are transformed through organized processes, machinery, and labor into finished goods or components.
-
B.
production facility
chosen
A production facility is a physical site equipped with machinery, resources, and personnel dedicated to manufacturing goods or processing materials at scale.
-
C.
semiconductor manufacturing facility
A semiconductor manufacturing facility is a highly controlled industrial plant where raw silicon wafers are processed through complex, precise, and cleanroom-based fabrication steps to produce integrated circuits and microchips.
-
D.
automotive joint venture
An automotive joint venture is a strategic business arrangement in which two or more companies collaborate to develop, produce, or distribute vehicles or related technologies while sharing resources, risks, and profits.
-
E.
Johnson & Johnson facility
A Johnson & Johnson facility is a physical site where the company conducts its operations, such as research, manufacturing, packaging, or distribution of healthcare and consumer products, under regulated quality and safety standards.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:49 a.m.