Triple

T437963
Position Surface form Disambiguated ID Type / Status
Subject Soviet Southwestern Front E10050 entity
Predicate reasonForDisbandment P13662 FINISHED
Object reorganization into Ukrainian Fronts 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: reorganization into Ukrainian Fronts | Statement: [Soviet Southwestern Front, reasonForDisbandment, reorganization into Ukrainian Fronts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForDisbandment
Context triple: [Soviet Southwestern Front, reasonForDisbandment, reorganization into Ukrainian Fronts]
  • A. reasonForDiscontinuation
    Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
  • B. decommissionedReason
    Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
  • C. reasonForElimination
    Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
  • D. reasonForDemolition
    Indicates the cause, justification, or circumstance that led to a structure or object being demolished.
  • E. reasonForWithdrawal
    Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
  • 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef26bb78819089b3b5dac0330619 completed Feb. 28, 2026, 1:35 p.m.
PD Predicate disambiguation batch_69a2eddb98e081909efcf9f0a955a908 completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2ee8b56d08190bd625626353d01b4 completed Feb. 28, 2026, 1:32 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.