Triple

T31336864
Position Surface form Disambiguated ID Type / Status
Subject L-twin E799197 entity
Predicate hasCrankshaftPosition P181447 FINISHED
Object shared crankshaft for both cylinders 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: shared crankshaft for both cylinders | Statement: [L-twin, hasCrankshaftPosition, shared crankshaft for both cylinders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCrankshaftPosition
Context triple: [L-twin, hasCrankshaftPosition, shared crankshaft for both cylinders]
  • A. crankshaftType
    Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
  • B. hasPubliclyAccessibleShaft
    Indicates that an entity possesses a shaft (such as a tunnel, elevator, or similar vertical/horizontal passage) that is accessible for use or entry by the general public.
  • C. camshaftConfiguration
    Indicates how the camshafts are arranged or configured within an engine’s valve train system.
  • D. camshaftType
    Indicates the specific design or configuration of camshaft associated with an engine or mechanical system.
  • E. hasCabPosition
    Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
  • F. None of above. chosen

Provenance (4 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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
PDg Predicate description generation batch_69f77648979c8190b6cdbb835ab8987c completed May 3, 2026, 4:22 p.m.
Created at: April 29, 2026, 9:16 p.m.