Triple
T21438828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Norihito, Prince Takamado |
E528885
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Norihito |
—
|
NE NERFINISHED |
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: Norihito | Statement: [Prince Norihito, Prince Takamado, givenName, Norihito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Norihito Context triple: [Prince Norihito, Prince Takamado, givenName, Norihito]
-
A.
Norihito
chosen
Norihito was a member of the Japanese Imperial Family better known by his title, Prince Takamado.
-
B.
Takahito
Takahito, better known by his title Prince Mikasa, was a member of the Japanese imperial family and the youngest son of Emperor Taishō.
-
C.
Yorihito
Yorihito was a Japanese imperial prince of the Higashifushimi-no-miya house who served as a high-ranking naval officer during the late Meiji and Taishō periods.
-
D.
Shintaro
Shintaro is a Japanese given name commonly used for males and borne by various notable figures in sports, entertainment, and politics.
-
E.
Katahito
Katahito was the personal name of Emperor Go-Yōzei, a late 16th- to early 17th-century Japanese emperor of the Azuchi–Momoyama and early Edo periods.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8140a1fc8190bedf297cfc4d4841 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 16, 2026, 6:04 p.m.