Triple
T10978563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uesugi clan |
E259435
|
entity |
| Predicate | statusInEdoPeriod |
P96426
|
FINISHED |
| Object | tozama daimyo |
—
|
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 daimyo | Statement: [Uesugi clan, statusInEdoPeriod, tozama daimyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInEdoPeriod Context triple: [Uesugi clan, statusInEdoPeriod, tozama daimyo]
-
A.
functionDuringEdoPeriod
Indicates that the function, role, or activity occurred specifically during Japan’s Edo period.
-
B.
statusInYomi
Indicates the role, rank, or condition an entity holds within the realm or context of Yomi.
-
C.
startOfEdoPeriod
Indicates that something marks the beginning or initial phase of the Edo period in Japanese history.
-
D.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
E.
statusInTemplePeriod
Indicates the role, condition, or standing that an entity held during the specified temple period.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f7b874819087bf5a858905279b |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.