Triple
T37561152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissan Technical Center |
E933821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nissan facility |
C44603
|
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: Nissan facility Context triple: [Nissan Technical Center, instanceOf, Nissan facility]
-
A.
Nissan design center
chosen
A Nissan design center is a specialized facility where multidisciplinary teams conceive, develop, and refine the aesthetic, functional, and ergonomic aspects of Nissan vehicles and related brand experiences.
-
B.
Toyota Motor Corporation facility
A Toyota Motor Corporation facility is any physical site owned or operated by Toyota where activities such as vehicle manufacturing, research and development, logistics, administration, sales, or service are conducted in support of the company’s automotive business.
-
C.
Yoshimoto Kogyo facility
A Yoshimoto Kogyo facility is a venue or complex owned or operated by the Japanese entertainment company Yoshimoto Kogyo, used for producing, rehearsing, and hosting performances, events, and related entertainment activities.
-
D.
Hyundai Motor Company facility
A Hyundai Motor Company facility is a physical site owned or operated by Hyundai where activities such as vehicle manufacturing, research and development, testing, logistics, administration, or customer service are conducted.
-
E.
Nissan vehicle
A Nissan vehicle is a motorized transportation product manufactured by Nissan, encompassing a range of cars, trucks, and SUVs designed for personal or commercial use.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.