Triple
T13145844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōji Yakusho |
E312331
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Kōji |
E797622
|
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: Kōji | Statement: [Kōji Yakusho, givenName, Kōji]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kōji Context triple: [Kōji Yakusho, givenName, Kōji]
-
A.
Kōji
chosen
Kōji is a Japanese masculine given name commonly used in various kanji spellings with meanings that vary depending on the characters chosen.
-
B.
Koichi
Koichi is a Japanese given name commonly used for males and borne by various notable figures in fields such as science, politics, and entertainment.
-
C.
Ryoji
Ryoji is a Japanese given name commonly used for males.
-
D.
Kodama Kōji
Kodama Kōji is a Japanese individual notable for bearing the surname Kodama, likely recognized for contributions in a specific professional or cultural field.
-
E.
Kentarō
Kentarō is a Japanese given name commonly used for males, often associated with traditional or strong-sounding name combinations.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98bcf6d0c819081d078f33e4bdedc |
completed | April 10, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5d809948190aced5ce377402463 |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:10 p.m.