Triple
T1561486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshihito |
E33333
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yoshihito |
E33333
|
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: Yoshihito | Statement: [Yoshihito, givenName, Yoshihito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yoshihito Context triple: [Yoshihito, givenName, Yoshihito]
-
A.
Yoshihito
chosen
Yoshihito was the 123rd Emperor of Japan, whose reign from 1912 to 1926 is known as the Taishō era, marked by political liberalization and cultural modernization.
-
B.
Nobutaka
Nobutaka is a Japanese masculine given name commonly borne by politicians, athletes, and other public figures.
-
C.
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.
-
D.
Yasuhiro
Yasuhiro is a Japanese masculine given name borne by various notable figures in politics, sports, and entertainment.
-
E.
Hirofumi
Hirofumi is a Japanese given name commonly borne by men, including notable contemporary politicians.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9088710a881909a1226e4b54311b8 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae891d41d88190aec6987c64c99757 |
completed | March 9, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:27 p.m.