Triple
T13336190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korechika Anami |
E317698
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Korechika |
E303297
|
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: Korechika | Statement: [Korechika Anami, givenName, Korechika]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Korechika Context triple: [Korechika Anami, givenName, Korechika]
-
A.
Korechika
chosen
Korechika is the given name of Anami Korechika, a Japanese military figure.
-
B.
Kōno Ichirō
Kōno Ichirō was an Imperial Japanese Army officer best known for his leadership role in commanding Japan’s 3rd Division.
-
C.
Kiichiro
Kiichiro is a Japanese given name most famously borne by Kiichiro Toyoda, the founder of Toyota Motor Corporation.
-
D.
Kinoshita Tōkichirō
Kinoshita Tōkichirō is the earlier name of Toyotomi Hideyoshi, the preeminent daimyo who unified Japan in the late 16th century.
-
E.
Noboru
Noboru is a Japanese masculine given name commonly borne by notable figures in politics, sports, and entertainment.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d00b75c8190af98784c7df904c8 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f730641f588190886119506e6dde8f |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:31 p.m.