Triple
T35467257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanagisawa clan |
E1025109
|
entity |
| Predicate | servedShogun |
P201594
|
FINISHED |
| Object | Tokugawa Tsunayoshi |
—
|
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: Tokugawa Tsunayoshi | Statement: [Yanagisawa clan, servedShogun, Tokugawa Tsunayoshi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedShogun Context triple: [Yanagisawa clan, servedShogun, Tokugawa Tsunayoshi]
-
A.
usedUnderShogun
Indicates that something was utilized or operated under the authority, control, or governance of a shogun.
-
B.
shōgun
Indicates that an entity holds the role or title of shōgun in relation to another entity, typically as its military ruler or supreme commander.
-
C.
lastShogun
Indicates that the subject is the final individual to hold the position or title of shogun in a given historical or organizational context.
-
D.
shogunalResidence
Indicates that one entity serves as the official residence or seat of authority for a shogun associated with another entity.
-
E.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
- F. None of above. chosen
Provenance (4 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
| PDg | Predicate description generation | batch_6a000a1c8f8881908293ab4f7207d25f |
completed | May 10, 2026, 4:31 a.m. |
Created at: May 3, 2026, 4:04 p.m.