Triple

T36563775
Position Surface form Disambiguated ID Type / Status
Subject Uesugi Kagekatsu E901914 entity
Predicate reducedStipendAfter P104885 FINISHED
Object Battle of Sekigahara 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: Battle of Sekigahara | Statement: [Uesugi Kagekatsu, reducedStipendAfter, Battle of Sekigahara]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reducedStipendAfter
Context triple: [Uesugi Kagekatsu, reducedStipendAfter, Battle of Sekigahara]
  • A. approximateStipend
    Indicates an estimated or rough amount of stipend associated with an entity or situation.
  • B. penaltyReducedTo chosen
    Indicates that an existing penalty has been lowered or commuted to a lesser penalty or amount.
  • C. stipendRank
    Indicates the relative ordering or level of a stipend assigned to an entity compared to others.
  • D. subsidizedInterest
    Indicates that the interest on a loan or financial obligation is partially or fully paid or reduced by a third party, typically a government or institution, rather than borne entirely by the borrower.
  • E. schoolMayReduceAmount
    Indicates that a school has the authority or ability to decrease a specified amount (such as a fee, payment, or allocation).
  • 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_69f76e634e9481908c9ba1b87ab87c26 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c477a4d481908f52e55b6688f60c completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:11 p.m.