Triple

T29656777
Position Surface form Disambiguated ID Type / Status
Subject Mongolia–Manchukuo border E750288 entity
Predicate outcomeOf1939Clashes P19109 FINISHED
Object Soviet–Mongolian victory 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: Soviet–Mongolian victory | Statement: [Mongolia–Manchukuo border, outcomeOf1939Clashes, Soviet–Mongolian victory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: outcomeOf1939Clashes
Context triple: [Mongolia–Manchukuo border, outcomeOf1939Clashes, Soviet–Mongolian victory]
  • A. contestedByDuringWWII
    Indicates that the entities were in opposition or conflict with each other during World War II.
  • B. sawClashesIn
    Indicates that an entity witnessed or experienced clashes or violent confrontations occurring in a particular location or context.
  • C. partOfConflictOutcome
    Indicates that one entity represents a specific component or aspect of the overall outcome of a conflict involving another entity.
  • D. resultOfBattle chosen
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • E. battleWasPartOf
    Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
  • 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_69f0d6226fe881908819197c9ef9ee04 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f697eabb048190bc01a830f14942c6 completed May 3, 2026, 12:33 a.m.
PD Predicate disambiguation batch_69f69664142c8190bc695501056b0236 completed May 3, 2026, 12:27 a.m.
Created at: April 28, 2026, 6:55 p.m.