Triple

T13601746
Position Surface form Disambiguated ID Type / Status
Subject Kerry Killinger E324958 entity
Predicate strategyImplemented P31887 FINISHED
Object aggressive expansion of Washington Mutual in the 1990s LITERAL FINISHED

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: aggressive expansion of Washington Mutual in the 1990s | Statement: [Kerry Killinger, strategyImplemented, aggressive expansion of Washington Mutual in the 1990s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strategyImplemented
Context triple: [Kerry Killinger, strategyImplemented, aggressive expansion of Washington Mutual in the 1990s]
  • A. implementedPlan
    Indicates that a specific plan has been carried out or put into effect by an entity.
  • B. strategyType chosen
    Indicates the specific kind or category of strategy associated with an entity or action.
  • C. missionStrategy
    Indicates the overarching plan, approach, or method an entity adopts to achieve a specific mission or objective.
  • D. aimedToImplement
    Indicates that an entity had the intention or plan to carry out, realize, or put another entity (such as a policy, idea, or system) into effect.
  • E. implementedPolicy
    Indicates that a particular policy has been put into effect or carried out by an entity.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb07ad3f48190a2173e42c5cfedb1 completed April 12, 2026, 2:47 p.m.
PD Predicate disambiguation batch_69dbae18eaf48190809e8b365856cde9 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:49 p.m.