Triple
T24181529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR stock cars |
E599437
|
entity |
| Predicate | approximateHorsepower |
P5894
|
FINISHED |
| Object | 650–750 hp |
—
|
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: 650–750 hp | Statement: [NASCAR stock cars, approximateHorsepower, 650–750 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateHorsepower Context triple: [NASCAR stock cars, approximateHorsepower, 650–750 hp]
-
A.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
C.
horsepower
chosen
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
D.
powerToWeightRatio
Indicates the relationship between an entity’s available power and its mass, expressing how much power is provided per unit of weight.
-
E.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.