Triple
T21153996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep-Eagle Division |
E521264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chrysler division |
C44619
|
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: Chrysler division Context triple: [Jeep-Eagle Division, instanceOf, Chrysler division]
-
A.
Renault division
A Renault division is an organizational unit within the Renault Group responsible for a specific set of activities, such as vehicle production, regional operations, or specialized services, managed under the broader corporate structure.
-
B.
member of the Chrysler family
A member of the Chrysler family is an individual who is biologically or legally related to the Chrysler lineage, historically associated with the founders and successors of the Chrysler automotive enterprise.
-
C.
Ford Motor Company division
A Ford Motor Company division is an organizational unit within Ford responsible for specific product lines, markets, or business functions, operating under the broader corporate structure and strategy of the company.
-
D.
Maserati division
Maserati division is a specialized organizational unit within the Maserati brand responsible for the design, production, marketing, and strategic management of its luxury performance vehicles and related services.
-
E.
Mercedes-Benz division
A Mercedes-Benz division is an organizational unit within the Mercedes-Benz company responsible for a specific product line, market segment, or operational function, such as passenger cars, commercial vehicles, or financial services.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.