Triple
T20666509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takahito, Prince Mikasa |
E507901
|
entity |
| Predicate | fullName |
P16
|
FINISHED |
| Object | Takahito |
—
|
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: Takahito | Statement: [Takahito, Prince Mikasa, fullName, Takahito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Takahito Context triple: [Takahito, Prince Mikasa, fullName, Takahito]
-
A.
Takahito
chosen
Takahito, better known by his title Prince Mikasa, was a member of the Japanese imperial family and the youngest son of Emperor Taishō.
-
B.
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.
-
C.
Taisuke
Taisuke is a Japanese given name notably borne by historical figures such as the Meiji-era politician Itagaki Taisuke.
-
D.
Tokihito
Tokihito, better known as Emperor Antoku, was a child emperor of Japan whose short reign ended tragically with his death during the Genpei War and the fall of the Taira clan.
-
E.
Takatoshi
Takatoshi is a masculine Japanese given name that can be written with various kanji combinations and is borne by multiple notable individuals in Japan.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c39dd48190965d65537592aef6 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.