Triple
T29558718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula Renault V6 |
E749976
|
entity |
| Predicate | carPowerOutput |
P6069
|
FINISHED |
| Object | approximately 330 bhp |
—
|
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: approximately 330 bhp | Statement: [Formula Renault V6, carPowerOutput, approximately 330 bhp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carPowerOutput Context triple: [Formula Renault V6, carPowerOutput, approximately 330 bhp]
-
A.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
B.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
vehiclePowerCollection
Indicates a relationship where a vehicle is associated with a set or collection of its power-related components, sources, or specifications.
-
D.
powertrainOutput
Indicates the relationship where a powertrain produces or delivers mechanical or electrical output (such as torque, power, or motion) to another component or system.
-
E.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1b59e481908e7a4676160788c0 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:18 p.m.