Triple
T17460453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daigo-tennō |
E425137
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Atsuhito |
—
|
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: Atsuhito | Statement: [Daigo-tennō, givenName, Atsuhito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atsuhito Context triple: [Daigo-tennō, givenName, Atsuhito]
-
A.
Atsuhito
chosen
Atsuhito was the personal name of Emperor Daigo, a 10th-century Japanese emperor of the Heian period.
-
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.
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.
Atsumori
Atsumori is a classical Noh play that dramatizes the tragic death and lingering spirit of the young warrior Taira no Atsumori during the Genpei War.
-
E.
Shintaro
Shintaro is a Japanese given name commonly used for males and borne by various notable figures in sports, entertainment, and politics.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3031c8190ab1dd0d41b002dd2 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:47 a.m.