Triple
T30026961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azai clan |
E762905
|
entity |
| Predicate | lastMainDaimyō |
P108858
|
FINISHED |
| Object | Azai Nagamasa |
—
|
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: Azai Nagamasa | Statement: [Azai clan, lastMainDaimyō, Azai Nagamasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMainDaimyō Context triple: [Azai clan, lastMainDaimyō, Azai Nagamasa]
-
A.
lastDaimyo
chosen
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
-
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.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
-
D.
firstDaimyo
Indicates that the subject is the first (initial or founding) daimyō associated with the specified domain, lineage, or context.
-
E.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679ac62ac8190b1ab93bf5803e0a9 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:48 p.m.