Triple

T35758183
Position Surface form Disambiguated ID Type / Status
Subject Cosworth DFV engine E1033501 entity
Predicate successor P78 FINISHED
Object Cosworth DFY engine
The Cosworth DFY engine is an evolution of the legendary DFV Formula One V8, refined for improved performance and reliability in early-1980s Grand Prix racing.
E1033501 NE 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: Cosworth DFY engine | Statement: [Cosworth DFV engine, successor, Cosworth DFY engine]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Cosworth DFY engine
Triple: [Cosworth DFV engine, successor, Cosworth DFY engine]
Generated description
The Cosworth DFY engine is an evolution of the legendary DFV Formula One V8, refined for improved performance and reliability in early-1980s Grand Prix racing.

Provenance (5 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_69f76e1262f48190a313318665acc189 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a1c138848190bdd27868794efd0f completed May 3, 2026, 7:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38915a6bd081908d6638afde1a31f7 completed June 22, 2026, 1:35 a.m.
NEDg Description generation batch_6a3892bb6a988190872dc116c08f6226 completed June 22, 2026, 1:41 a.m.
NED2 Entity disambiguation (via description) batch_6a389318ff248190b94e729cc46e55b5 completed June 22, 2026, 1:42 a.m.
Created at: May 3, 2026, 4:06 p.m.