Triple
T23673774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimazu clan |
E584809
|
entity |
| Predicate | statusDuringEdo |
P96426
|
FINISHED |
| Object | tozama daimyō |
—
|
LITERAL 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: tozama daimyō | Statement: [Shimazu clan, statusDuringEdo, tozama daimyō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringEdo Context triple: [Shimazu clan, statusDuringEdo, tozama daimyō]
-
A.
statusInEdoPeriod
chosen
Indicates the social, political, or legal standing an entity held specifically during Japan’s Edo period.
-
B.
functionDuringEdoPeriod
Indicates that the function, role, or activity occurred specifically during Japan’s Edo period.
-
C.
statusInJapan
Indicates the legal, social, or official standing or condition an entity holds specifically within the context of Japan.
-
D.
statusInYomi
Indicates the role, rank, or condition an entity holds within the realm or context of Yomi.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- F. None of above.
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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f1dee08190bfe78564c65f01ad |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.