Triple
T26340754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaga Domain |
E662638
|
entity |
| Predicate | daimyoStatus |
P160260
|
FINISHED |
| Object | tozama |
—
|
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 | Statement: [Kaga Domain, daimyoStatus, tozama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daimyoStatus Context triple: [Kaga Domain, daimyoStatus, tozama]
-
A.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
B.
lastDaimyo
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
-
C.
daimyoResidence
Indicates that a location serves or served as the official residence of a daimyo (feudal lord).
-
D.
daimyoHouseUnder
Indicates that one daimyo’s house is subordinate to or under the authority or control of another house.
-
E.
daimyōFamily
Indicates a familial relationship involving a daimyō, such as belonging to or being part of a daimyō’s family.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa2af708190a41199a1bd022ed2 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:38 p.m.