Triple
T4978397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Gigafactory network |
E111823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tesla infrastructure |
C5180
|
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: Tesla infrastructure Context triple: [Tesla Gigafactory network, instanceOf, Tesla infrastructure]
-
A.
Tesla factory
chosen
A Tesla factory is a large-scale, highly automated manufacturing facility where Tesla designs, produces, and assembles electric vehicles and related components such as batteries and powertrains.
-
B.
electric vehicle charging network
An electric vehicle charging network is a coordinated system of charging stations, infrastructure, and management services that supplies power to electric vehicles across multiple locations.
-
C.
electric vehicle platform
An electric vehicle platform is a modular, shared chassis architecture that integrates the battery pack, electric motors, suspension, and core electronics to serve as the foundation for multiple EV models.
-
D.
battery electric vehicle architecture
Battery electric vehicle architecture is the integrated system design that defines how the battery pack, electric drivetrain, power electronics, control systems, and supporting components are configured and interact to deliver propulsion, safety, efficiency, and functionality in an all-electric vehicle.
-
E.
battery electric city car
A battery electric city car is a compact, fully electric vehicle designed primarily for short urban trips, featuring a small footprint, limited range, and zero tailpipe emissions.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:33 p.m.