Triple
T35467272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanagisawa clan |
E1025109
|
entity |
| Predicate | typeOfDaimyō |
P160260
|
FINISHED |
| Object | fudai (hereditary vassal) 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: fudai (hereditary vassal) daimyō | Statement: [Yanagisawa clan, typeOfDaimyō, fudai (hereditary vassal) daimyō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDaimyō Context triple: [Yanagisawa clan, typeOfDaimyō, fudai (hereditary vassal) daimyō]
-
A.
daimyōFamily
Indicates a familial relationship involving a daimyō, such as belonging to or being part of a daimyō’s family.
-
B.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
C.
daimyoStatus
chosen
Indicates that one entity holds the status or role of a daimyo in relation to another entity or context.
-
D.
daimyoDomain
Indicates that a daimyo holds authority or control over a particular domain.
-
E.
firstDaimyo
Indicates that the subject is the first (initial or founding) daimyō associated with the specified domain, lineage, or context.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:04 p.m.