Triple

T25475140
Position Surface form Disambiguated ID Type / Status
Subject Strela-2 E638410 entity
Predicate engagementAspectLimitations P90556 FINISHED
Object primarily rear-aspect engagements 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: primarily rear-aspect engagements | Statement: [Strela-2, engagementAspectLimitations, primarily rear-aspect engagements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: engagementAspectLimitations
Context triple: [Strela-2, engagementAspectLimitations, primarily rear-aspect engagements]
  • A. engagementRange
    Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
  • B. engagementOf
    Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
  • C. engagementCapability
    Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
  • D. showsLimitationOf
    Indicates that one entity reveals, demonstrates, or makes apparent the limitations, weaknesses, or constraints of another entity.
  • E. activitiesRestricted chosen
    Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
  • 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_69e75db9b964819096802dcf502e577e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f754447c8190acc16c440f8bb03d completed May 2, 2026, 1:08 p.m.
PD Predicate disambiguation batch_69f468421ba08190880eac99135e5970 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 2:25 p.m.