Triple
T24522309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishida Mitsunari |
E606565
|
entity |
| Predicate | roleAtSekigahara |
P148259
|
FINISHED |
| Object | commander-in-chief of the Western Army |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: commander-in-chief of the Western Army | Statement: [Ishida Mitsunari, roleAtSekigahara, commander-in-chief of the Western Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtSekigahara Context triple: [Ishida Mitsunari, roleAtSekigahara, commander-in-chief of the Western Army]
-
A.
sideInBattleOfSekigahara
chosen
Indicates that an entity participated as a side or faction in the Battle of Sekigahara.
-
B.
roleInEdoPeriod
Indicates that an entity held a specific role, position, or function during Japan’s Edo period.
-
C.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
D.
roleInMeijiRestoration
Indicates the specific part, function, or contribution an entity had in bringing about or shaping the Meiji Restoration.
-
E.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
- F. None of above.
Provenance (3 batches)
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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.