Triple

T24976452
Position Surface form Disambiguated ID Type / Status
Subject Raleigh Chopper E625034 entity
Predicate hasSafetyCriticism P53756 FINISHED
Object stability issues at low speed 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: stability issues at low speed | Statement: [Raleigh Chopper, hasSafetyCriticism, stability issues at low speed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSafetyCriticism
Context triple: [Raleigh Chopper, hasSafetyCriticism, stability issues at low speed]
  • A. hasCriticism
    Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
  • B. hasTargetOfCritique
    Indicates that one entity is the object or focus of another entity’s criticism or evaluative critique.
  • C. criticizedFor
    Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
  • D. sometimesCriticizedFor chosen
    Indicates that an entity is on occasion the target of criticism for a particular reason, behavior, or attribute.
  • E. hasSafetyReputation
    Indicates that one entity is associated with an assessment or record of safety-related reliability or trustworthiness.
  • 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_69e2ff254570819093d197b1900305ac completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f47b865df48190bf4b6d3e9f9305e6 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f4682c8a3c8190adbfaac99474eaaf completed May 1, 2026, 8:45 a.m.
Created at: April 18, 2026, 6:02 a.m.