Triple

T416122
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Yugoslavia (pro-Axis government) E9595 entity
Predicate countryInConflict P13112 FINISHED
Object Yugoslavia in World War II 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: Yugoslavia in World War II | Statement: [Kingdom of Yugoslavia (pro-Axis government), countryInConflict, Yugoslavia in World War II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countryInConflict
Context triple: [Kingdom of Yugoslavia (pro-Axis government), countryInConflict, Yugoslavia in World War II]
  • A. involvedCountry
    Indicates that a country participates in, is associated with, or is otherwise implicated in the referenced event, activity, or situation.
  • B. militaryConflict
    Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
  • C. warParticipatedIn chosen
    Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
  • D. countryAttacker
    Indicates that one country is the aggressor or initiator of an attack against another country.
  • E. countryAttacked
    Indicates that one country has carried out an attack against another country.
  • 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_69a2e80111fc8190961d5b7c6154123f completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eebde1d881908fb212bfba9d7c67 completed Feb. 28, 2026, 1:33 p.m.
PD Predicate disambiguation batch_69a2edcff4688190809d83d112ff25a5 completed Feb. 28, 2026, 1:29 p.m.
Created at: Feb. 28, 2026, 1:09 p.m.