Triple
T34607588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōei era |
E888636
|
entity |
| Predicate | shōgun |
P179695
|
FINISHED |
| Object | Tokugawa Tsunayoshi |
E1013044
|
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: Tokugawa Tsunayoshi | Statement: [Hōei era, shōgun, Tokugawa Tsunayoshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shōgun Context triple: [Hōei era, shōgun, Tokugawa Tsunayoshi]
-
A.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
B.
lastShogun
Indicates that the subject is the final individual to hold the position or title of shogun in a given historical or organizational context.
-
C.
shogunateName
Indicates the name assigned to a particular shogunate.
-
D.
lastDaimyo
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
-
E.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
- F. None of above. chosen
Provenance (5 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a374114010c8190b41612e81a2661f8 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.