Triple
T14997326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 久米邦武 |
E373991
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Kume Kunitake |
E76479
|
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: Kume Kunitake | Statement: [久米邦武, name, Kume Kunitake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kume Kunitake Context triple: [久米邦武, name, Kume Kunitake]
-
A.
Kume Kunitake
chosen
Kume Kunitake was a Meiji-era Japanese scholar, historian, and statesman best known for documenting the Iwakura Mission’s journey and for his influential writings on Japan’s modernization.
-
B.
Tsunehito
Tsunehito was the personal name of Emperor Kameyama, a 13th-century Japanese emperor of the Kamakura period.
-
C.
Kiyotaka
Kiyotaka is a Japanese given name commonly used for males and borne by various notable figures in Japan.
-
D.
Kuranosuke
Kuranosuke is the given name of Ōishi Kuranosuke, the historical leader of the Forty-seven rōnin in early 18th-century Japan.
-
E.
Toshimichi
Toshimichi is a Japanese given name most famously borne by Ōkubo Toshimichi, a key statesman and leader of the Meiji Restoration.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ebe275c819094473d37cf33c7d0 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 2:54 a.m.