Triple
T13488438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Andreyevich Baranov |
E318567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian colonial administrator |
C20737
|
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 colonial administrator Context triple: [Alexander Andreyevich Baranov, instanceOf, Russian colonial administrator]
-
A.
Japanese colonial administrator
A Japanese colonial administrator is an official appointed by the Japanese government to govern, manage, and implement imperial policies in occupied or colonized territories.
-
B.
British colonial administrator
A British colonial administrator is an official appointed by the British government to govern, manage, and implement imperial policies in overseas colonies, overseeing local administration, law, and economic exploitation.
-
C.
Dutch colonial administrator
A Dutch colonial administrator is an official appointed by the Netherlands to govern, manage, and oversee political, economic, and social affairs in its overseas colonies.
-
D.
colonial officer
chosen
A colonial officer is an official appointed by a colonial power to administer, govern, and enforce its policies and interests within a colonized territory.
-
E.
colonial ruler
A colonial ruler is an authority figure who governs and controls a foreign territory and its people on behalf of a distant imperial power, often exploiting local resources and enforcing unequal power structures.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:42 p.m.