Triple
T8337750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisahito |
E195830
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hisahito |
E195830
|
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: Hisahito | Statement: [Hisahito, givenName, Hisahito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hisahito Context triple: [Hisahito, givenName, Hisahito]
-
A.
Hisahito
chosen
Hisahito is a Japanese imperial prince and the only grandson of Emperor Naruhito’s predecessor, Emperor Emeritus Akihito, placing him in the direct line of succession to the Chrysanthemum Throne.
-
B.
Masahito
Masahito is the personal name of Prince Hitachi, a member of the Japanese imperial family and younger brother of Emperor Emeritus Akihito.
-
C.
Tadahiko
Tadahiko is a Japanese masculine given name used by various notable individuals in fields such as sports, arts, and academia.
-
D.
Yasuhiro
Yasuhiro is a Japanese masculine given name borne by various notable figures in politics, sports, and entertainment.
-
E.
Yasuhiko
Yasuhiko is a Japanese given name notably borne by Prince Asaka Yasuhiko, a member of the Imperial Family of Japan in the early 20th century.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd5027c81909724f25aa30bbe58 |
completed | March 31, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf5127db38819087d5ba71b6064998 |
completed | April 3, 2026, 5:33 a.m. |
Created at: March 30, 2026, 5:57 p.m.