Triple
T17446324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tata Steel |
E424793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flagship company of Tata Group |
C10991
|
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: flagship company of Tata Group Context triple: [Tata Steel, instanceOf, flagship company of Tata Group]
-
A.
Indian company
chosen
An Indian company is a business entity incorporated or registered in India under applicable Indian corporate laws, conducting commercial, industrial, or professional activities within or outside the country.
-
B.
Samsung Group subsidiary
A Samsung Group subsidiary is a company that is owned or controlled by the Samsung conglomerate and operates in one of its diverse business sectors under the broader Samsung corporate umbrella.
-
C.
Saudi Arabian company
A Saudi Arabian company is a business entity established and operating under the laws and regulations of the Kingdom of Saudi Arabia, typically engaged in commercial, industrial, or service activities within domestic and international markets.
-
D.
Indian government agency
An Indian government agency is an official public-sector organization established by the Government of India to implement laws, deliver services, regulate specific domains, or execute policy and administrative functions at the national or regional level.
-
E.
Vinci Group subsidiary
A Vinci Group subsidiary is a company that is majority-owned or controlled by Vinci Group and operates under its strategic, financial, and governance framework while conducting specific business activities within the group’s overall portfolio.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.