Triple

T2243127
Position Surface form Disambiguated ID Type / Status
Subject Kido Butai E49440 entity
Predicate statusByLateWar P19322 FINISHED
Object effectively destroyed as an elite carrier force 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: effectively destroyed as an elite carrier force | Statement: [Kido Butai, statusByLateWar, effectively destroyed as an elite carrier force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusByLateWar
Context triple: [Kido Butai, statusByLateWar, effectively destroyed as an elite carrier force]
  • A. legalStatusAfterWar
    Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
  • B. statusDuringWar chosen
    Indicates the role, condition, or classification an entity held specifically during a period of war.
  • C. concludedWar
    Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
  • D. laterStatus
    Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
  • E. endedBilateralWarBetween
    Indicates that an action or event brought a bilateral war between two parties to a conclusion or cessation.
  • 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_69a88aa979788190ad6500f1d8eee2fc completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc0c157e88190a5bc876d9591a24b completed March 7, 2026, 6:08 a.m.
PD Predicate disambiguation batch_69abbdb160248190aa75b38f11ad8602 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:47 p.m.