Triple

T19958029
Position Surface form Disambiguated ID Type / Status
Subject Supersport motorcycle E479736 entity
Predicate oftenSubjectTo P65116 FINISHED
Object higher insurance premiums 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 insurance premiums | Statement: [Supersport motorcycle, oftenSubjectTo, higher insurance premiums]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenSubjectTo
Context triple: [Supersport motorcycle, oftenSubjectTo, higher insurance premiums]
  • A. isSubjectTo
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • B. oftenHeldToBe
    Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
  • C. decisionsSubjectTo
    Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
  • D. oftenTargetedBy
    Indicates that an entity is frequently chosen or subjected as the object of another entity’s actions, attention, or attacks.
  • E. oftenUndergo chosen
    Indicates that an entity frequently experiences, is subjected to, or passes through a particular process, action, or change.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65af1b32c81908ebe0e2570ec06a9 completed April 20, 2026, 4:57 p.m.
PD Predicate disambiguation batch_69e537f7e4848190b431a69ec3f1b609 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:54 p.m.