Triple

T32177753
Position Surface form Disambiguated ID Type / Status
Subject Cummins B Series engines E821899 entity
Predicate governedSpeedRange P156872 FINISHED
Object approximately 2500–3000 rpm 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: approximately 2500–3000 rpm | Statement: [Cummins B Series engines, governedSpeedRange, approximately 2500–3000 rpm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governedSpeedRange
Context triple: [Cummins B Series engines, governedSpeedRange, approximately 2500–3000 rpm]
  • A. governingSpeedRange chosen
    Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
  • B. hasSpeedLimitRange
    Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
  • C. hasSpeedRegime
    Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
  • D. hasVariableSpeedLimits
    Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
  • E. hasSpeedLimitCharacteristic
    Indicates that an entity is associated with a specific speed limit property or constraint.
  • 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_69f3490755288190aee11740a34862f9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 completed May 10, 2026, 7:54 a.m.
PD Predicate disambiguation batch_6a0038e525448190a4c815f51595e78d completed May 10, 2026, 7:51 a.m.
Created at: May 1, 2026, 12:34 a.m.