Triple
T4627437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minamoto no Yoshitsune |
E101132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese military commander |
C449
|
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 military commander Context triple: [Minamoto no Yoshitsune, instanceOf, Japanese military commander]
-
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.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
-
C.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
D.
Japanese military personnel of World War II
Individuals who served in the armed forces of the Empire of Japan during World War II, including the Imperial Japanese Army, Navy, and associated military organizations.
-
E.
Japanese statesman
A Japanese statesman is a political leader or public official who plays a significant role in shaping Japan’s governmental policies, diplomatic relations, and national development.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.