Triple
T35091440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meitoku |
E1012734
|
entity |
| Predicate | usedUnderShogun |
P182512
|
FINISHED |
| Object | Ashikaga Yoshimitsu |
—
|
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: Ashikaga Yoshimitsu | Statement: [Meitoku, usedUnderShogun, Ashikaga Yoshimitsu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUnderShogun Context triple: [Meitoku, usedUnderShogun, Ashikaga Yoshimitsu]
-
A.
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.
-
B.
shogunateName
Indicates the name assigned to a particular shogunate.
-
C.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
D.
hasNotableShogun
Indicates that an entity is associated with a historically notable shogun, such as by rule, leadership, or significant connection.
-
E.
roleInEdoPeriod
Indicates that an entity held a specific role, position, or function during Japan’s Edo 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.