Triple

T5509982
Position Surface form Disambiguated ID Type / Status
Subject Daimler-Benz DB 600 E144537 entity
Predicate connectingRodArrangement P65157 FINISHED
Object fork-and-blade connecting rods 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: fork-and-blade connecting rods | Statement: [Daimler-Benz DB 600, connectingRodArrangement, fork-and-blade connecting rods]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectingRodArrangement
Context triple: [Daimler-Benz DB 600, connectingRodArrangement, fork-and-blade connecting rods]
  • A. wheelArrangementSystem
    Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
  • B. cylinderArrangement
    Indicates how multiple cylinders are positioned or organized relative to one another.
  • C. shaftCount
    Indicates the number of shafts associated with or contained in an object or system.
  • D. shaftOrientation
    Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
  • E. wingCouplingMechanism
    Indicates the type or presence of a structural or functional mechanism by which wings are linked or coupled to each other or to another body part during use.
  • 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_69c008f6b5048190a09064116062cf69 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f4ba90c8190ad22e5de84c545f9 completed March 22, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69c01b07bde08190b3933b96bdc70dd5 completed March 22, 2026, 4:38 p.m.
PDg Predicate description generation batch_69c01f051e508190b3886d87b4afdd0b completed March 22, 2026, 4:55 p.m.
Created at: March 22, 2026, 3:33 p.m.