Triple

T4375660
Position Surface form Disambiguated ID Type / Status
Subject Siege of Kumamoto Castle E98999 entity
Predicate strengthAttackers P47565 FINISHED
Object approximately 13,000 rebels 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: approximately 13,000 rebels | Statement: [Siege of Kumamoto Castle, strengthAttackers, approximately 13,000 rebels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthAttackers
Context triple: [Siege of Kumamoto Castle, strengthAttackers, approximately 13,000 rebels]
  • A. attackerStrength chosen
    Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
  • B. strengthPeak
    Indicates the point or period at which an entity’s strength reaches its maximum level.
  • C. strengthDescription
    Indicates a description or characterization of the degree of strength associated with an entity or relationship.
  • D. strengthType
    Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
  • E. mainAttacker
    Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another 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_69b3454ea8f48190a49c2436624d6ef6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b352222df48190bead639e99635faf completed March 12, 2026, 11:54 p.m.
PD Predicate disambiguation batch_69b34f557fe8819085032bf7f0cea5dc completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:18 p.m.