Triple

T38027921
Position Surface form Disambiguated ID Type / Status
Subject Ashikaga Yoshimi E948829 entity
Predicate successorInShogunate P202874 FINISHED
Object Ashikaga Yoshihisa 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 Yoshihisa | Statement: [Ashikaga Yoshimi, successorInShogunate, Ashikaga Yoshihisa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorInShogunate
Context triple: [Ashikaga Yoshimi, successorInShogunate, Ashikaga Yoshihisa]
  • A. successorAsDaijoDaijin
    Indicates that one individual succeeded another in holding the position of Daijō-daijin (Chancellor of the Realm) in the Japanese imperial government.
  • B. successorInJapan
    Indicates that one entity directly follows or replaces another in a role, position, or sequence within the context of Japan.
  • C. successorAsDaimyoOfHikone
    Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
  • D. predecessorAsDaimyoOfHikone
    Indicates that one entity previously held the position of daimyō (feudal lord) of Hikone immediately before the other entity.
  • E. successorAsLordOf
    Indicates that one entity takes over the role or title of lord from another entity, becoming their direct successor in that lordship.
  • 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_69f76efd1bc48190a729097fe5177b61 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a00c9ddd62881909859a36b114a4132 completed May 10, 2026, 6:09 p.m.
PD Predicate disambiguation batch_6a00c939b88881909d5353db4265e572 completed May 10, 2026, 6:06 p.m.
PDg Predicate description generation batch_6a00c9dd1eac8190b33c620ddfae7981 completed May 10, 2026, 6:09 p.m.
Created at: May 3, 2026, 4:20 p.m.