Triple
T36115211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRMN |
E1044599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toyota brand |
C62655
|
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: Toyota brand Context triple: [GRMN, instanceOf, Toyota brand]
-
A.
Toyota brand subline
A Toyota brand subline is a distinct product or model range within the Toyota brand that targets a specific market segment, feature set, or customer need while remaining under the overarching Toyota identity.
-
B.
Toyota vehicle platform
A Toyota vehicle platform is a shared engineering and structural foundation used across multiple Toyota and Lexus models to standardize components, improve manufacturing efficiency, and enhance performance and safety.
-
C.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
-
D.
Toyota Group company
A Toyota Group company is any corporation that is directly or indirectly controlled by, affiliated with, or strategically partnered with Toyota Motor Corporation as part of its broader corporate group.
-
E.
Chevrolet brand
Chevrolet brand is a globally recognized American automotive marque known for producing a wide range of vehicles—from affordable compact cars and family SUVs to performance sports cars and trucks—emphasizing practicality, value, and broad market appeal.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.