Triple

T35202792
Position Surface form Disambiguated ID Type / Status
Subject Combino Plus E1016453 entity
Predicate structuralDesignGoal P49728 FINISHED
Object higher fatigue strength 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: higher fatigue strength | Statement: [Combino Plus, structuralDesignGoal, higher fatigue strength]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: structuralDesignGoal
Context triple: [Combino Plus, structuralDesignGoal, higher fatigue strength]
  • A. engineeringGoal chosen
    Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
  • B. overallDesignGoal
    Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
  • C. structuralDesign
    Indicates the relationship in which an entity is responsible for planning, organizing, or defining the structural configuration or framework of another entity.
  • D. appliesToDesignGoal
    Indicates that something (such as a method, rule, or constraint) is relevant or intended to be used for achieving a particular design goal.
  • E. lifetimeDesignGoal
    Indicates a design objective or target that is intended to be maintained or achieved over the entire lifetime of the system or product.
  • 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_69f76dde814c8190a71f60d514a424a4 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f63c8788190b253a18de5ca1312 completed May 3, 2026, 6:09 p.m.
PD Predicate disambiguation batch_69f78e2d71248190b850c2802ec170c0 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:02 p.m.