Triple
T15900981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa Yoshinobu |
E385586
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Mito Domain |
E702234
|
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: Mito Domain | Statement: [Tokugawa Yoshinobu, residence, Mito Domain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mito Domain Context triple: [Tokugawa Yoshinobu, residence, Mito Domain]
-
A.
Mito Domain
chosen
Mito Domain was a prominent feudal han of the Tokugawa shogunate based in Mito, Ibaraki, and ruled by a branch of the Tokugawa family.
-
B.
Hatogaya Domain
Hatogaya Domain was a small feudal han of the Edo period in Japan, located in what is now part of Asaka in Saitama Prefecture.
-
C.
Tosa Domain
Tosa Domain was a feudal han in Shikoku during Japan’s Edo period, ruled by the Yamauchi clan and later known for producing influential Meiji-era political leaders.
-
D.
Kubota Domain
Kubota Domain was a feudal han of Edo-period Japan centered in present-day Akita Prefecture and ruled by the Satake clan.
-
E.
Morioka Domain
Morioka Domain was a feudal han of northern Japan’s Edo period, ruled by the Nanbu clan from its castle town of Morioka in present-day Iwate Prefecture.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563cd2f081909404d724ecc8785a |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb04f3ea08190b5581768770677e8 |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.