Triple
T3532431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roshen |
E74690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian company |
C9186
|
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: Ukrainian company Context triple: [Roshen, instanceOf, Ukrainian company]
-
A.
Austrian company
An Austrian company is a business entity legally registered and operating under the corporate laws and regulations of Austria, typically headquartered or having significant operations within Austrian territory.
-
B.
European company
chosen
A European company is a business entity legally registered and operating within one or more countries of Europe, subject to European and relevant national regulations, markets, and cultural contexts.
-
C.
Ukrainian person
A Ukrainian person is an individual who identifies with the nation of Ukraine through citizenship, heritage, culture, or self-identification, often sharing Ukrainian language, traditions, and historical experiences.
-
D.
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.
-
E.
Indian company
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.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:19 p.m.