Triple

T25106331
Position Surface form Disambiguated ID Type / Status
Subject Russian Helicopters E628875 entity
Predicate roleInRussia P167248 FINISHED
Object key defense industrial asset 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: key defense industrial asset | Statement: [Russian Helicopters, roleInRussia, key defense industrial asset]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInRussia
Context triple: [Russian Helicopters, roleInRussia, key defense industrial asset]
  • A. roleInSovietUnion
    Indicates that an entity held a specific position, function, or status within the governmental, political, or institutional structure of the Soviet Union.
  • B. roleDuringRussianCivilWar
    Indicates the specific function, position, or involvement an entity had during the period of the Russian Civil War.
  • C. roleInRepublic
    Indicates that an entity holds or plays a specific role or function within a republic or republican system.
  • D. positionOnRussia
    Indicates the stance, opinion, or policy that one entity holds regarding Russia.
  • E. roleInGeorgia
    Indicates that an entity holds or has held a specific role, position, or function within the context of Georgia (such as its government, institutions, or organizations).
  • 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_69e2ff3071548190b62d1ac237397197 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f66a6468ec8190a43ed6cd8c797f42 completed May 2, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69f66598d6008190a7ca8ff80399fd34 completed May 2, 2026, 8:59 p.m.
PDg Predicate description generation batch_69f6691da93081909deaf680614fc900 completed May 2, 2026, 9:14 p.m.
Created at: April 18, 2026, 6:26 a.m.