Triple

T15814212
Position Surface form Disambiguated ID Type / Status
Subject Pratt & Whitney Wasp E383432 entity
Predicate boreStroke P87198 FINISHED
Object bore 5.75 in, stroke 5.75 in (approximate for R‑1340 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: bore 5.75 in, stroke 5.75 in (approximate for R‑1340 variant) | Statement: [Pratt & Whitney Wasp, boreStroke, bore 5.75 in, stroke 5.75 in (approximate for R‑1340 variant)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boreStroke
Context triple: [Pratt & Whitney Wasp, boreStroke, bore 5.75 in, stroke 5.75 in (approximate for R‑1340 variant)]
  • A. boreStrokeDesign chosen
    Indicates that an engine’s bore and stroke configuration is designed or specified in a particular way.
  • B. cylinderBore
    Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
  • C. pistonStroke
    Indicates the distance or movement range that a piston travels within a cylinder during one complete stroke.
  • D. hasBoreType
    Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
  • E. bore
    Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a1571881909488728f123865ad completed April 16, 2026, 11:14 a.m.
PD Predicate disambiguation batch_69e0053b847c8190945726c3ddac21cc completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.