Triple

T27523436
Position Surface form Disambiguated ID Type / Status
Subject Yugoslav People’s Army barracks E694771 entity
Predicate sometimesBesiegedDuring P36192 FINISHED
Object Croatian War of Independence NE NERFINISHED

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: Croatian War of Independence | Statement: [Yugoslav People’s Army barracks, sometimesBesiegedDuring, Croatian War of Independence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sometimesBesiegedDuring
Context triple: [Yugoslav People’s Army barracks, sometimesBesiegedDuring, Croatian War of Independence]
  • A. wasBesiegedBy
    Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
  • B. besiegedIn chosen
    Indicates that one entity is under siege at, or during the event of, another specified location or time.
  • C. siegeOccurredIn
    Indicates that a siege took place within or at the location specified by the related entity.
  • D. siegeRelated
    Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
  • E. sieged
    Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
  • 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_69ef538550208190aa9de8e2cb260d93 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f6359e3d3c81909814e2f0a7fb0ea9 completed May 2, 2026, 5:34 p.m.
PD Predicate disambiguation batch_69f631871c888190bf29466fe4254e51 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 1:22 p.m.