Triple
T601827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akihito |
E11509
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Fumihito |
E87550
|
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: Fumihito | Statement: [Akihito, child, Fumihito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fumihito Context triple: [Akihito, child, Fumihito]
-
A.
Fumihito
chosen
Fumihito is the Crown Prince of Japan and younger son of Emperor Emeritus Akihito, serving as first in line to the Chrysanthemum Throne.
-
B.
Harukichi
Harukichi is a Japanese given name most notably borne by Harukichi Hyakutake, an Imperial Japanese Navy admiral during World War II.
-
C.
Shōhō
Shōhō was a Japanese light aircraft carrier of the Imperial Japanese Navy during World War II, notable for being the first Japanese carrier sunk in the war during the Battle of the Coral Sea.
-
D.
Yamamoto
Yamamoto is a Japanese surname most famously associated with Admiral Isoroku Yamamoto, the commander-in-chief of the Imperial Japanese Navy during World War II.
-
E.
Takuma Tono
Takuma Tono was a Japanese landscape architect known for bringing traditional Japanese garden design to international prominence, including in the United States.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49d7c08648190bbffc8adb4148987 |
completed | March 1, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a66662e848819095aca23ceb5eeef2 |
completed | March 3, 2026, 4:41 a.m. |
Created at: March 1, 2026, 7:35 p.m.