Triple

T9119569
Position Surface form Disambiguated ID Type / Status
Subject 2.5L Duratec inline-4 E218808 entity
Predicate boreStrokeDesign P87198 FINISHED
Object undersquare or near-square design (varies by variant) 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: undersquare or near-square design (varies by variant) | Statement: [2.5L Duratec inline-4, boreStrokeDesign, undersquare or near-square design (varies by variant)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boreStrokeDesign
Context triple: [2.5L Duratec inline-4, boreStrokeDesign, undersquare or near-square design (varies by variant)]
  • A. cylinderBore
    Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
  • B. boltDesign
    Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
  • C. hasBoreType
    Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
  • D. crankshaftType
    Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
  • E. numberOfCylinders
    Indicates the count of engine cylinders associated with an entity.
  • 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_69ca83dddd548190983b96c664f7f367 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8a902e08190a7eb4728f32b9e1d completed April 1, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69cc66003e3c819091e1e42c9cf7c781 completed April 1, 2026, 12:25 a.m.
PDg Predicate description generation batch_69cc6a3c78388190a7436acc0e44ff55 completed April 1, 2026, 12:43 a.m.
Created at: March 30, 2026, 7:17 p.m.