Triple
T38603936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akō Domain |
E934292
|
entity |
| Predicate | daimyō |
P169391
|
FINISHED |
| Object | Asano Naganori |
—
|
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: Asano Naganori | Statement: [Akō Domain, daimyō, Asano Naganori]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daimyō Context triple: [Akō Domain, daimyō, Asano Naganori]
-
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
Indicates that one entity holds the status or role of a daimyo in relation to another entity or context.
-
D.
daimyoDomain
chosen
Indicates that a daimyo holds authority or control over a particular domain.
-
E.
shōgun
Indicates that an entity holds the role or title of shōgun in relation to another entity, typically as its military ruler or supreme commander.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.