Triple
T15893244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koichi |
E385381
|
entity |
| Predicate | commonAlternativeSpelling |
P457
|
FINISHED |
| Object | Kōichi |
E385381
|
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ōichi | Statement: [Koichi, commonAlternativeSpelling, Kōichi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kōichi Context triple: [Koichi, commonAlternativeSpelling, Kōichi]
-
A.
Koichi
chosen
Koichi is a Japanese given name commonly used for males and borne by various notable figures in fields such as science, politics, and entertainment.
-
B.
Kunihiko
Kunihiko is a Japanese masculine given name commonly borne by notable figures in fields such as mathematics, animation, and the arts.
-
C.
Kentarō
Kentarō is a Japanese given name commonly used for males, often associated with traditional or strong-sounding name combinations.
-
D.
Toshiaki
Toshiaki is a Japanese masculine given name commonly used for men and boys in Japan.
-
E.
Yojiro
Yojiro 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563727cc819086b5c18b655dd7f6 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009183a94081909c5892b1ccbc1d7a |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 4:51 a.m.