Triple
T4822086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Mikasa |
E107733
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Takahito |
E507901
|
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: Takahito | Statement: [Prince Mikasa, givenName, Takahito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Takahito Context triple: [Prince Mikasa, givenName, 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.
Taisuke
Taisuke is a Japanese given name notably borne by historical figures such as the Meiji-era politician Itagaki Taisuke.
-
C.
Shintaro
Shintaro is a Japanese given name commonly used for males and borne by various notable figures in sports, entertainment, and politics.
-
D.
Masahito
Masahito is the personal name of Prince Hitachi, a member of the Japanese imperial family and younger brother of Emperor Emeritus Akihito.
-
E.
Atsuhito
Atsuhito was the personal name of Emperor Daigo, a 10th-century Japanese emperor of the Heian period.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6caa95ec8190bea525dbf3a00477 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf10a7fcc881908d46c39854d1cbdb |
completed | March 21, 2026, 9:42 p.m. |
Created at: March 20, 2026, 1:24 p.m.