Triple
T22504549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArcelorMittal Nippon Steel India |
E556355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | company based in India |
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: company based in India Context triple: [ArcelorMittal Nippon Steel India, instanceOf, company based in India]
-
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.
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.
-
C.
organization based in Russia
An organization based in Russia is any structured group or entity—such as a company, nonprofit, institution, or association—whose primary operations, legal registration, or headquarters are located within the Russian Federation.
-
D.
Polish company
A Polish company is a business entity established and operating under Polish law, typically registered in Poland and engaged in commercial, industrial, or service activities within domestic and/or international markets.
-
E.
Israeli company
An Israeli company is a business entity established and operating under the laws of Israel, typically headquartered or significantly active within the Israeli economy and subject to its regulatory, tax, and corporate governance frameworks.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.