Triple
T25576470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yodo Castle |
E641119
|
entity |
| Predicate | governingShogunate |
P179182
|
FINISHED |
| Object | Tokugawa shogunate |
—
|
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 shogunate | Statement: [Yodo Castle, governingShogunate, Tokugawa shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingShogunate Context triple: [Yodo Castle, governingShogunate, Tokugawa shogunate]
-
A.
shogunateName
Indicates the name assigned to a particular shogunate.
-
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.
lastDaimyo
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
-
D.
daimyoDomain
Indicates that a daimyo holds authority or control over a particular domain.
-
E.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 21, 2026, 4:01 p.m.