Triple
T8750974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Manchuria Railway Company |
E207953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese colonial enterprise |
C1415
|
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: Japanese colonial enterprise Context triple: [South Manchuria Railway Company, instanceOf, Japanese colonial enterprise]
-
A.
Japanese colonial administration
Japanese colonial administration refers to the governmental, military, and bureaucratic systems established by the Empire of Japan to control, exploit, and assimilate its overseas territories from the late 19th century through World War II.
-
B.
colonial enterprise
chosen
A colonial enterprise is an organized venture, typically led by a state or chartered company, that establishes control over foreign territories and peoples to extract resources, labor, and strategic advantage.
-
C.
Japanese organization
A Japanese organization is a structured group based in Japan that coordinates people and resources to achieve shared goals, typically reflecting Japanese cultural norms, business practices, and social values.
-
D.
Japanese organization
A Japanese organization is a structured group based in Japan that coordinates people and resources to achieve shared goals, typically reflecting Japanese cultural, legal, and business practices.
-
E.
Japanese military administration unit
A Japanese military administration unit is an organizational entity within Japan’s armed forces responsible for managing logistics, personnel, planning, and support functions necessary to sustain military operations.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:39 p.m.