Triple

T37841280
Position Surface form Disambiguated ID Type / Status
Subject Alchevsk Iron and Steel Works E943483 entity
Predicate regionConflictContext P21190 FINISHED
Object Donbas conflict zone 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: Donbas conflict zone | Statement: [Alchevsk Iron and Steel Works, regionConflictContext, Donbas conflict zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionConflictContext
Context triple: [Alchevsk Iron and Steel Works, regionConflictContext, Donbas conflict zone]
  • A. conflictRegion chosen
    Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
  • B. conflictContext
    Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
  • C. endedConflictInRegion
    Indicates that an entity brought a conflict within a specified region to an end.
  • D. conflictRule
    Indicates that two or more rules, conditions, or constraints are incompatible or interfere with each other when applied together.
  • E. postConflictContext
    Indicates that the relationship or action occurs within, or is shaped by, a setting that follows the end of an armed conflict or violent confrontation.
  • 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_69f76eeb0f7081908d6d3adbc469889c completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a0079e152648190a9da2add94fc1831 completed May 10, 2026, 12:28 p.m.
PD Predicate disambiguation batch_6a0078f77f9c8190af357a6016a2bd53 completed May 10, 2026, 12:24 p.m.
Created at: May 3, 2026, 4:19 p.m.