Triple
T22614774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Higashikuni Kunihiko |
E566813
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Kunihiko |
—
|
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: Kunihiko | Statement: [Higashikuni Kunihiko, hasGivenName, Kunihiko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kunihiko Context triple: [Higashikuni Kunihiko, hasGivenName, Kunihiko]
-
A.
Kunihiko
chosen
Kunihiko is a Japanese masculine given name commonly borne by notable figures in fields such as mathematics, animation, and the arts.
-
B.
Naruhiko
Naruhiko was a Japanese imperial prince and army general who briefly served as Prime Minister of Japan at the end of World War II.
-
C.
Tadahiko
Tadahiko is a Japanese masculine given name used by various notable individuals in fields such as sports, arts, and academia.
-
D.
Kenjirō
Kenjirō is a Japanese masculine given name that can be written with various kanji combinations and is borne by multiple notable individuals in fields such as sports, arts, and entertainment.
-
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 (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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f167ecc7188190bf41fe2177d48e6c |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:58 p.m.