Triple
T6399920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postwar revival of Ford Motor Company |
E144035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate restructuring program |
C10117
|
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: corporate restructuring program Context triple: [Postwar revival of Ford Motor Company, instanceOf, corporate restructuring program]
-
A.
corporate restructuring strategy
chosen
A corporate restructuring strategy is a comprehensive plan that realigns a company’s organizational structure, operations, and assets to improve efficiency, financial performance, and long-term competitiveness.
-
B.
M&A deal
An M&A deal is a transaction in which one company acquires or merges with another to combine assets, operations, and ownership for strategic, financial, or operational benefits.
-
C.
corporate board
A corporate board is a group of individuals elected by shareholders to oversee a company's management, set strategic direction, and ensure accountability and compliance with laws and regulations.
-
D.
corporate control struggle
A corporate control struggle is a conflict among stakeholders, such as executives, board members, or shareholders, competing to influence or determine the strategic direction and decision-making authority of a company.
-
E.
post–World War II reconstruction program
A post–World War II reconstruction program is a coordinated set of policies, financial aid, and institutional reforms designed to rebuild war-torn economies, infrastructure, and governance structures while promoting long-term stability and growth.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:35 p.m.