Triple
T36437457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelby GT500 (2020–2022) |
E897626
|
entity |
| Predicate | horsepowerMetric |
P6069
|
FINISHED |
| Object | 567 kW |
—
|
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: 567 kW | Statement: [Shelby GT500 (2020–2022), horsepowerMetric, 567 kW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: horsepowerMetric Context triple: [Shelby GT500 (2020–2022), horsepowerMetric, 567 kW]
-
A.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
B.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
D.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
E.
powerToWeightRatio
Indicates the relationship between an entity’s available power and its mass, expressing how much power is provided per unit of weight.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.