Triple
T14337217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunihiko Kodaira |
E355495
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object |
Kunihiko
Kunihiko is a Japanese masculine given name commonly borne by notable figures in fields such as mathematics, animation, and the arts.
|
E1168971
|
NE FINISHED |
How this triple was built (4 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: [Kunihiko Kodaira, givenName, Kunihiko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kunihiko Context triple: [Kunihiko Kodaira, givenName, Kunihiko]
-
A.
Tadahiko
Tadahiko is a Japanese masculine given name used by various notable individuals in fields such as sports, arts, and academia.
-
B.
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.
-
C.
Kentarō
Kentarō is a Japanese given name commonly used for males, often associated with traditional or strong-sounding name combinations.
-
D.
Shintaro
Shintaro is a Japanese given name commonly used for males and borne by various notable figures in sports, entertainment, and politics.
-
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. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kunihiko Triple: [Kunihiko Kodaira, givenName, Kunihiko]
Generated description
Kunihiko is a Japanese masculine given name commonly borne by notable figures in fields such as mathematics, animation, and the arts.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Kunihiko Target entity description: Kunihiko is a Japanese masculine given name commonly borne by notable figures in fields such as mathematics, animation, and the arts.
-
A.
Tadahiko
Tadahiko is a Japanese masculine given name used by various notable individuals in fields such as sports, arts, and academia.
-
B.
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.
-
C.
Kentarō
Kentarō is a Japanese given name commonly used for males, often associated with traditional or strong-sounding name combinations.
-
D.
Shintaro
Shintaro is a Japanese given name commonly used for males and borne by various notable figures in sports, entertainment, and politics.
-
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. chosen
Provenance (5 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff677935408190a28af4cd34d82aa4 |
completed | May 9, 2026, 4:57 p.m. |
| NEDg | Description generation | batch_69ff67f64d2c81908fd2d8a09cd0b369 |
completed | May 9, 2026, 4:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff6888a85481909e8cdd34ed230fa4 |
completed | May 9, 2026, 5:02 p.m. |
Created at: April 10, 2026, 1:14 a.m.