Triple
T3188926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamamoto Gonnohyōe |
E66770
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Yamamoto |
E12160
|
NE 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: Yamamoto | Statement: [Yamamoto Gonnohyōe, familyName, Yamamoto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamamoto Context triple: [Yamamoto Gonnohyōe, familyName, Yamamoto]
-
A.
Yamamoto
chosen
Yamamoto is a Japanese surname most famously associated with Admiral Isoroku Yamamoto, the commander-in-chief of the Imperial Japanese Navy during World War II.
-
B.
Yamashita
Yamashita is a Japanese surname most famously associated with General Tomoyuki Yamashita, a prominent Imperial Japanese Army commander during World War II.
-
C.
Tanaka
Tanaka is a common Japanese surname borne by numerous notable figures in politics, arts, sports, and other fields.
-
D.
Yasuhiko
Yasuhiko is a Japanese given name notably borne by Prince Asaka Yasuhiko, a member of the Imperial Family of Japan in the early 20th century.
-
E.
Yoshihisa
Yoshihisa is a Japanese given name commonly used for males.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e491508190bc881feaee3889bc |
completed | March 8, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b511f9d8dc8190bc3728e75dec1059 |
completed | March 14, 2026, 7:44 a.m. |
Created at: March 8, 2026, 3:06 p.m.