Triple
T30611766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igor Sechin |
E779196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian businessperson |
C8802
|
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: Russian businessperson Context triple: [Igor Sechin, instanceOf, Russian businessperson]
-
A.
Russian public figure
chosen
A Russian public figure is an individual who holds a prominent, recognizable role in Russian society—such as in politics, media, culture, or business—and whose actions and opinions attract significant public and media attention.
-
B.
Chinese businessman
A Chinese businessman is an individual from China engaged in commercial, industrial, or entrepreneurial activities, typically involved in managing or investing in businesses within domestic or international markets.
-
C.
British businessperson
A British businessperson is an individual from the United Kingdom engaged in commercial, industrial, or professional business activities, typically involved in managing, owning, or operating enterprises for profit.
-
D.
Qatari businessperson
A Qatari businessperson is an individual from Qatar engaged in commercial, industrial, or professional business activities, often involved in regional or international trade, investment, or entrepreneurship.
-
E.
Japanese businessperson
A Japanese businessperson is an individual from Japan engaged in commercial, corporate, or entrepreneurial activities, typically operating within Japan’s distinct business culture and practices.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:26 p.m.