Triple
T13635892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Go-Shirakawa |
E325847
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Masahito |
E168497
|
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: Masahito | Statement: [Emperor Go-Shirakawa, givenName, Masahito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Masahito Context triple: [Emperor Go-Shirakawa, givenName, Masahito]
-
A.
Masahito
chosen
Masahito is the personal name of Prince Hitachi, a member of the Japanese imperial family and younger brother of Emperor Emeritus Akihito.
-
B.
Yasuhiro
Yasuhiro is a Japanese masculine given name borne by various notable figures in politics, sports, and entertainment.
-
C.
Takahito
Takahito, better known by his title Prince Mikasa, was a member of the Japanese imperial family and the youngest son of Emperor Taishō.
-
D.
Yoshihisa
Yoshihisa is a Japanese given name commonly used for males.
-
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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe729a48288190bf24503af6522677 |
completed | May 8, 2026, 11:32 p.m. |
Created at: April 9, 2026, 9:51 p.m.