Triple
T23500664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hideki Kuriyama |
E571830
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hideki |
—
|
NE NERFINISHED |
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: Hideki | Statement: [Hideki Kuriyama, givenName, Hideki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hideki Context triple: [Hideki Kuriyama, givenName, Hideki]
-
A.
Hideki
chosen
Hideki is a Japanese given name most famously borne by theoretical physicist Hideki Yukawa, the first Japanese Nobel Prize laureate.
-
B.
Tadamichi
Tadamichi is a Japanese given name historically borne by notable figures such as the Heian-period court noble Fujiwara no Tadamichi.
-
C.
Hiroo
Hiroo is an upscale residential and shopping district in central Tokyo known for its international community, embassies, cafes, and boutiques.
-
D.
Hiroo
Hiroo is a coastal town in Hokkaido, Japan, known for its fishing industry and scenic Pacific shoreline.
-
E.
Jisaburo
Jisaburo is a Japanese given name most notably borne by Admiral Jisaburo Ozawa, a prominent Imperial Japanese Navy commander during World War II.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a8fc37908190af86a01ab85737d6 |
completed | April 29, 2026, 6:45 a.m. |
Created at: April 17, 2026, 6:06 p.m.